Apparatus, systems and methods for online, multi-carrier, multi-service parcel shipping management

ABSTRACT

The present invention provides apparatus, systems and methods providing a single system available over a global communications network for shipping management for each parcel from a plurality of parcels that each Shipper of a plurality of Shippers ships using any one of a plurality of services offered by any one of a plurality of carriers.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority of U.S. Provisional Patent ApplicationSer. No. 60/158,179, filed on Oct. 6, 1999, U.S. Provisional PatentApplication Ser. No. 60/170,186, filed on Dec. 10, 1999, U.S.Provisional Patent Application Ser. No. 60/170,504, filed on Dec. 13,1999, U.S. Provisional Patent Application Ser. No. 60/192,692, filed onMar. 28, 2000, U.S. Provisional Patent Application Ser. No. 60/192,723,filed on Mar. 27, 2000, U.S. Provisional Patent Application Ser. No.60/193,899, filed on Mar. 31, 2000, and U.S. Provisional PatentApplication Ser. No. 60/195,748, filed on Apr. 6, 2000. The disclosuresof U.S. Provisional Patent Application Ser. No. 60/158,179, filed onOct. 6, 1999, U.S. Provisional Patent Application Ser. No. 60/170,186,filed on Dec. 10, 1999, U.S. Provisional Patent Application Ser. No.60/170,504, filed on Dec. 13, 1999, are incorporated for all purposesherein by reference as if fully stated here.

FIELD OF THE INVENTION

The field of the present invention is computer systems, and specificallycomputer systems for parcel shipping management.

BACKGROUND OF THE INVENTION

Individuals, small businesses and major corporations the (“Shipper(s)”)ship billions of parcels every year (small office/home office shippersare referred to as “SOHO” Shippers). Each parcel, also sometimesreferred to herein as a package, is shipped by a Shipper using at leastone parcel carrier (the “carrier(s)”, or “Carrier(s)”).

Each parcel is characterized by a set of “Parcel Specifications.” Parcelspecifications include but are not limited to such factors as: parceldimensions, parcel weight, parcel value and the like.

Each Shipper is faced with certain shipping requirements and limitations(“Shipping Requirements”), such as the location from which the parcel isto be shipped, time frame within which the particular parcel must arriveat its destination, the ability of the shipper to drop off the parcel,budgetary constraints with regard to the cost of shipping, insuranceagainst loss, delivery notification, loss protection, and the like.

Each Carrier has its own unique rating schedule, and delivery and pickuprules and schedules for each of a multitude of different services. Insome cases, a particular Carrier's rules may be available in astandalone Carrier-provided paper-based or computer system. ManyShippers attempt to work with each of the standalone, individualpaper-based and computer Carrier-provided systems (“standalone Carriersystem environment”) in order to ship a parcel.

A Shipper that uses standalone Carrier systems must sort through thevarious services offered by each carrier and apply each Carrier's rulesto determine whether one or more carriers offer a service with which todeliver a particular parcel according to the Shipper's requirements. Ifthe Shipper determines that more than one carrier offers a service withwhich to deliver a particular parcel according to the Shipper'srequirements, then the particular Shipper might additionally beconcerned with selecting a carrier and service that provide shippingservices at the optimal price.

A single system available over the Internet is needed for Shippers thatprovides shipping management for each parcel that each Shipper needs toship using any one of a plurality of services offered by any one of aplurality of carriers.

SUMMARY OF THE INVENTION

The present invention provides apparatus, systems and methods providinga single system available over the Internet that provides shippingmanagement for each parcel that each Shipper of a plurality of Shippersneeds to ship using any one of a plurality of services offered by anyone of a plurality of carriers.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features of the present invention are more fully setforth in the following description of exemplary embodiments of theinvention. The description is presented with reference to theaccompanying drawings in which:

FIG. 1 is an entity relationship diagram depicting the interfacerelationships provided by the System between Shippers as Sellers,Carriers, Recipients as Buyers, eCommerce/eAuction Providers and theSystem in an exemplary embodiment of the System in an independent systemeCommerce environment;

FIG. 2 is an entity relationship diagram depicting the interfacerelationships provided by the System between Shippers, Carriers,Recipients and the System in an exemplary embodiment of the System in anInternet environment;

FIG. 3 is a graphic representation depicting an exemplary user computerconfiguration and the user computer's interface with the System in anInternet environment;

FIG. 4 is a simplified schematic diagram of a user's computer and theinterface between the user's computer and the System servers using theInternet in an exemplary embodiment of the invention in an Internetenvironment;

FIG. 5 is a simplified graphic representation of an exemplaryconfiguration of the System, and relationships between the System andCarriers and Users, in an exemplary embodiment of the System in anindependent system eCommerce environment;

FIG. 6 is a simplified graphic representation depicting an alternateview of the System Data Center and its interfaces in an exemplaryembodiment of the System in an independent system eCommerce environment;

FIG. 7 is a simplified graphic representation of an exemplaryconfiguration of the System, and relationships between the System andCarriers and Shippers/Users, in an exemplary simplified Internetembodiment of the invention;

FIG. 8 is a high level System component diagram depicting an exemplarySystem Architecture in an exemplary embodiment of the System in anInternet environment;

FIG. 9 is a graphic representation of an exemplary menu architecture forthe System in an exemplary embodiment of the System in an independentsystem eCommerce environment;

FIGS. 10A through 10E are high level logic flow diagrams depicting thelogic flow for processing both Shipper/Seller and Buyer/Bidderinformation in an exemplary embodiment of the System in an independentsystem eCommerce environment;

FIG. 11 is a graphic representation depicting an exemplary embodiment ofa registration introduction screen in an exemplary embodiment of theSystem in an independent system eCommerce environment;

FIG. 12 is a graphic representation depicting an exemplary embodiment ofa User address collection screen in an exemplary embodiment of theSystem in an independent system eCommerce environment;

FIG. 13 is a graphic representation of an exemplary embodiment of aShipping Location screen in an exemplary embodiment of the System in anindependent system eCommerce environment;

FIG. 14 is a graphic representation depicting an exemplary embodiment ofa Locations screen in an exemplary embodiment of the System in anindependent system eCommerce environment;

FIG. 15 is a graphic representation depicting an alternative exemplaryembodiment of a Locations screen inset in an alternative exemplaryembodiment of the System in an Internet environment;

FIG. 16 is a graphic representation of an exemplary embodiment of a UPSregistration screen in an exemplary embodiment of the System in anindependent system eCommerce environment;

FIG. 17 is a graphic representation of an exemplary embodiment of aneCommerce registration introduction screen in an exemplary embodiment ofthe System in an independent system eCommerce environment;

FIG. 18 is a graphic representation of a registration complete screen inan exemplary embodiment of the System in an independent system eCommerceenvironment;

FIG. 19 is a graphic representation of an exemplary embodiment of theSeller's Carrier/Service Preferences Screen in an exemplary embodimentof the System in an independent system eCommerce environment;

FIG. 20 is a graphic representation of an alternative embodiment of theSeller's Carrier/Service Preferences Screen in an exemplary embodimentof the System in an independent system eCommerce environment;

FIG. 21 is a graphic representation of an exemplary embodiment of aSeller's Charges and Payment Preferences Screen in an exemplaryembodiment of the System in an independent system eCommerce environment;

FIG. 22 is a graphic representation of an alternative embodiment of theSeller's Charges and Payment Preferences Screen in an exemplaryembodiment of the System in an independent system eCommerce environment;

FIG. 23 is a System interactivity data and logic flow diagram depictingan exemplary embodiment of the Seller's eCommerce Registration processin an exemplary embodiment of the System in an independent systemeCommerce environment;

FIG. 24 is a graphic representation of a Registration Needs CompletionScreen in an exemplary embodiment of the System in an independent systemeCommerce environment;

FIG. 25 is a graphic representation of an exemplary embodiment of aCreate a Seller's Link Screen in an exemplary embodiment of the Systemin an independent system eCommerce environment;

FIG. 26 is a graphic representation of an alternative online screen thatcollects a user's shipping specifications and preferences in analternative exemplary embodiment of the System in an Internetenvironment;

FIGS. 27A through 27C are high level logic flow diagrams controlcommunications with client machine peripheral devices in an exemplaryembodiment of the System in an Internet environment;

FIG. 28 is a graphic representation of an alternative online screen thatcollects supplemental user shipping specifications and preferences in analternative exemplary embodiment of the System in an Internetenvironment;

FIG. 29 is a graphic representation of an alternative embodiment of aCreate a Seller's Link Screen in an exemplary embodiment of the Systemin an independent system eCommerce environment;

FIG. 30 depicts an exemplary alternative embodiment of the Create aSeller's Link screen in an exemplary embodiment of the System in anindependent system eCommerce environment;

FIG. 31 depicts the text of an exemplary hypertext link such as iscreated by an exemplary embodiment of the “Create Link” feature in anexemplary embodiment of the System in an independent system eCommerceenvironment;

FIG. 32 is a graphic representation depicting an alternative embodimentof a hyperlink generated by the System in an exemplary embodiment of theSystem in an independent system eCommerce environment;

FIGS. 33A and 33B represent a database schema diagram that depicts anexemplary embodiment of tables in which data is stored by the Systemregarding a particular Seller Account in an exemplary embodiment of theSystem in an independent system eCommerce environment;

FIG. 34 is a graphic representation of an exemplary embodiment of aSeller's eCommerce/eAuction web site page in an exemplary embodiment ofthe System in an independent system eCommerce environment;

FIG. 35 is a graphic representation of an exemplary Buyer shippingrating information collection screen that the Buyer would see upon entryinto the System in an exemplary embodiment of the System in anindependent system eCommerce environment;

FIG. 36A is a graphic representation depicting an exemplary embodimentof a dynamically dimensioned, multi-carrier, multi-service shippingrates comparison Graphic Array in an exemplary embodiment of the Systemin an independent system eCommerce environment;

FIGS. 36B through 36E are high level data retrieval logic flow diagramsdepicting the data and high level logic that the system uses tocalculate a shipping rate;

FIG. 36F is a graphic representation of an alternative exemplary PreviewRates Screen (also referred to in some embodiments as a Rates and TimesScreen) in an alternative exemplary embodiment of the invention;

FIGS. 37A and 37B represent a System interactivity data and logic flowdiagram depicting an exemplary embodiment of the Create Link and theBuyer's Preview Shipping Rates functionality in an exemplary embodimentof the System in an independent system eCommerce environment;

FIG. 38 is a high level flow diagram depicting an overview of the Systemlogic to generate a dynamically dimensioned, multi-carrier,multi-service shipping rates comparison Graphic Array in an exemplaryembodiment of the System in an Internet environment;

FIGS. 39A through 39C are high level flow diagrams depicting the initialtiming and rating logic to develop a dynamically dimensioned,multi-carrier, multi-service shipping rates comparison Graphic Array inan exemplary embodiment of the System in an Internet environment;

FIG. 40 is a graphic representation depicting an exemplary embodiment ofa multi-carrier, multi-service shipping rates comparison Graphic Arrayin an exemplary embodiment of the System in an independent systemeCommerce environment;

FIG. 41 is a graphic representation of a Seller's Buyer InformationScreen in an exemplary embodiment of the System in an independent systemeCommerce environment;

FIG. 42 is a graphic representation of an exemplary embodiment of aSubject Parcel data screen in an exemplary embodiment of the System inan independent system eCommerce environment;

FIG. 43 is a graphic representation of an exemplary embodiment of aSystem-prepared e-mail to the Buyer in an exemplary embodiment of theSystem in an independent system eCommerce environment;

FIG. 44 is a graphic representation of an exemplary embodiment of theBuyer Response Introduction screen in an exemplary embodiment of theSystem in an independent system eCommerce environment;

FIG. 45 is a graphic representation of an exemplary embodiment of theBuyer Shipping Information Collection screen in an exemplary embodimentof the System in an independent system eCommerce environment;

FIG. 46 is a graphic representation depicting an alternative exemplaryembodiment of a dynamically dimensioned, multi-carrier, multi-serviceshipping rates comparison Graphic Array in an alternative exemplaryembodiment of the System in an independent system eCommerce environment;

FIG. 47 is a graphic representation depicting an exemplary embodiment ofa Shipping Summary Screen in an exemplary embodiment of the System in anindependent system eCommerce environment;

FIG. 48 is a graphic representation depicting an alternative exemplaryembodiment of a Shipping Summary Screen in an exemplary embodiment ofthe System in an Internet environment;

FIG. 49 is a graphic representation depicting an exemplary embodiment ofa Cardholder Information collection screen in an exemplary embodiment ofthe System in an independent system eCommerce environment;

FIG. 50 is a graphic representation depicting an exemplary embodiment ofa System's Shipping Log in an exemplary embodiment of the System in anindependent system eCommerce environment;

FIG. 51 is a graphic representation depicting an exemplary embodiment ofa Seller notification e-mail in an exemplary embodiment of the System inan independent system eCommerce environment;

FIG. 52 is a graphic representation of an exemplary embodiment of a VoidPackage screen in an exemplary embodiment of the System in anindependent system eCommerce environment;

FIG. 53 is a graphic representation of an exemplary embodiment of aReprint Label screen in an exemplary embodiment of the System in anindependent system eCommerce environment;

FIG. 54 is a high level flow diagram depicting an exemplary embodimentof Label Printing in an exemplary embodiment of the System in anInternet environment;

FIG. 55 is a high level flow diagram depicting an exemplary embodimentof Image Printing in an exemplary embodiment of the System in anInternet environment;

FIGS. 56 through 58 are graphic representations of exemplary onlinescreens with which a user controls the final shipping and label printingfor a particular package in an alternative exemplary embodiment in anInternet environment;

FIG. 59 is a graphic representation of an exemplary embodiment of a SendShip Notification screen in an exemplary embodiment of the System in anindependent system eCommerce environment;

FIG. 60 is a graphic representation of an alternative exemplaryembodiment of a Send Ship Notification screen in an alternativeexemplary embodiment of the System in an Internet environment;

FIG. 61 is a graphic representation depicting an exemplary embodiment ofa Ship a Package Summary online report in an exemplary embodiment of theSystem in an independent system eCommerce environment;

FIG. 62 is a graphic representation depicting an exemplary embodiment ofa UPS End-of-Day Screen in an exemplary embodiment of the System in anindependent system eCommerce environment;

FIG. 63 is a graphic representation of an exemplary embodiment of aReprint Driver Record Screen in an exemplary embodiment of the System inan independent system eCommerce environment;

FIGS. 64A-1, 64A-2, 64B-1 and 64B-2 are System interactivity data andlogic flow diagrams depicting an exemplary embodiment of the process bywhich the System completes the information necessary to ship a packagein an exemplary embodiment of the System in an independent systemeCommerce environment;

FIGS. 65A and 65B represent a database schema diagram that depicts anexemplary embodiment of tables in which data is stored by the Systemregarding a particular package and a particular Seller's Account in anexemplary embodiment of the System in an independent system eCommerceenvironment;

FIG. 66 depicts an exemplary XML formatted request for submitting atracking request to a Carrier in an exemplary embodiment of the Systemin an Internet environment;

FIG. 67 depicts an exemplary successful tracking response, also in XMLformat, returned by the Carrier in an exemplary embodiment of the Systemin an Internet environment;

FIG. 68 is a graphic representation of a Shipper online user inputscreen that is displayed on the Shipper's display screen in an exemplaryembodiment of the System in an Internet environment;

FIG. 69 is a logic flow diagram that depicts the high level logic fortracking the status of a particular package in an exemplary embodimentof the System in an Internet environment;

FIG. 70 is a graphic representation of an exemplary embodiment of aTracking Failure Report Screen in an exemplary embodiment of the Systemin an Internet environment;

FIG. 71 is a graphic representation of an exemplary embodiment of aSuccessful Tracking Report Screen for a package with Delivered status inan exemplary embodiment of the System in an Internet environment;

FIG. 72 is a graphic representation of an exemplary embodiment of aSuccessful Tracking Report Screen for a package with non-final status inan exemplary embodiment of the System in an Internet environment;

FIG. 73 is a graphic representation of an exemplary CMS online userinput screen in an exemplary embodiment of the System in an Internetenvironment;

FIG. 74 is a graphic representation of an exemplary CMS display screenthat reports a successful tracking result in an exemplary embodiment ofthe System in an Internet environment;

FIG. 75 is a graphic representation of an exemplary CMS error trackingreport display screen in an exemplary embodiment of the System in anInternet environment;

FIG. 76 is a graphic representation of an exemplary embodiment of a “MyTracking” Screen in an exemplary embodiment of the System in an Internetenvironment;

FIG. 77 is a graphic representation of an exemplary embodiment of aShipping Log Screen;

FIG. 78 is a graphic representation of an exemplary embodiment of aDetailed Shipping Log Entry Screen in an exemplary embodiment of theSystem in an Internet environment;

FIG. 79 is a graphic representation of an exemplary embodiment of adetailed “Quick Track” result screen in an exemplary embodiment of theSystem in an Internet environment;

FIG. 80 is a graphic display of an exemplary embodiment of an “AddInbound Packages” Screen in an exemplary embodiment of the System in anInternet environment;

FIG. 81 is a graphic representation of an exemplary embodiment of a“View Inbound Packages” Summary Screen in an exemplary embodiment of theSystem in an Internet environment; and

FIG. 82 is a graphic representation of a View Inbound Packages DetailScreen in an exemplary embodiment of the System in an Internetenvironment.

DETAILED DESCRIPTION OF THE INVENTION

A portion of the disclosure of this patent document, including but notlimited to the renderings of graphic user interface displays in FIGS.10A through 10E, FIGS. 11 through 22, FIGS. 24 through 26, FIGS. 28through 30, FIGS. 34 through 35, FIG. 36A, FIG. 36F, FIGS. 40 through53, FIGS. 56 through 63, FIG. 68, and FIGS. 70 through 82, containsmaterial which is subject to copyright protection by Stamps.com, Inc.Stamps.com, Inc. has no objection to the facsimile reproduction byanyone of the patent document or the patent disclosure, as it appears inthe Patent and Trademark Office patent file or records, but otherwisereserves all copyright rights whatsoever.

“iShip.com™” (sometimes also referred to herein as “ISHIP.COM” or simplyas “iShip.com”), “iShip™” (sometimes also referred to herein as “ISHIP”or simply as “iShip”), “The Internet Package Shipper™” (sometimes alsoreferred to herein as “THE INTERNET PACKAGE SHIPPER” or simply as “TheInternet Package Shipper”), “Price It™” (sometimes also referred toherein as “PRICE IT” or simply as “Price It”), “Sell It™” (sometimesalso referred to herein as “SELL IT” or simply as “Sell It”), “TrackIt™” (sometimes also referred to herein as “TRACK IT” or simply as“Track It”), “Ship It™” (sometimes referred to herein as “SHIP IT” orsimply as “Ship It”), “Shipping Tools™” (sometimes referred to herein as“SHIPPING TOOLS” or simply as “Shipping Tools”), “My iShip™” (sometimesreferred to herein as “MY ISHIP” of simply as “My iShip”) and associatedlogos are trademarks of Stamps.com, Inc. The names of actual companiesand products mentioned herein may be the trademarks of their respectiveowners.

A. CONTEXTUAL OVERVIEW OF EXEMPLARY EMBODIMENT TYPES

Two types of exemplary Internet-related embodiments of the inventionwill be described herein: 1.) an exemplary simplified Internetembodiment; and 2.) an exemplary electronic commerce (“eCommerce”)embodiment. Because these two types of embodiments differ somewhat inuser interface interaction features and flow, a brief perspectiveoverview of these two exemplary embodiment types is provided below.

1. Exemplary Simplified Internet Embodiment

In the exemplary simplified Internet embodiment of the invention, asystem (the “System”) exemplifying features of the invention provides asingle automated computer interface between users of the system who areshippers of parcels (“Shippers”) and multiple carriers of parcels(“Carriers”). Each Shipper, using a client computer device, accesses theSystem over a global communications network such as the Internet. EachShipper uses the System to arrange for, and manage the shipment of, oneor more parcels. Each shipment arranged by a Shipper is performed by aparticular Carrier, using a particular service offered by thatparticular Carrier. References herein to the words “parcel” and“package” include letters, and larger items (see, e.g., FIG. 15 belowand Packaging types 1043 (Carrier Letter), 1044 (Carrier Pak), 1046(Carrier Box), 1047 (Carrier Tube), and 1045 (Other Packaging)).

Each Carrier may provide one or more types of shipment services, suchas, for example, Next Day, Two-Day, etc. Each parcel shipped by theShipper is shipped to a particular Recipient. Each supported Carrier hasa unique rating schedule, delivery and pickup rules and schedules, andcertification requirements (the “Carrier Rules”).

In the exemplary simplified Internet embodiment, the Shipper providesall information required by the System to facilitate the shipping ofeach parcel to be shipped by a Carrier designated by the Shipper; therecipient, once provided with a tracking number can access the System totrack the status of a package but is not called upon to provide anyinformation necessary to facilitate or manage the shipment. As isfurther described below, the provision of information by the Shipper inthe exemplary simplified Internet embodiment differs from the exemplaryeCommerce embodiment, in which both the Shipper (also referred to as the“Seller”) and the Recipient (also referred to as the “Buyer”) provideinformation to the System to facilitate and manage a particularshipment.

2. Exemplary eCommerce Embodiment

In an eCommerce embodiment of the invention, the Shipper is a seller(the “Seller”) of goods through a particular eCommerce or electronicAuction (“eAuction”) provider (eCommerce or eAuction web site). TheSeller/Shipper registers with a particular eCommerce/eAuction provider(the “Provider”) at the Provider's Web site to sell, advertise, orotherwise describe, one or more items that the Seller/Shipper hopes tosell or award to the highest bidder using an electronic auctionfacility.

As opposed to the exemplary simplified Internet embodiment where allinformation necessary for arranging a particular shipment is provided bythe Shipper, in the exemplary eCommerce embodiment of the invention, theSystem prompts different individuals to provide information necessary torate and ship a particular parcel.

The Seller/Shipper (sometimes referred to herein simply as the “Seller,”or as the “Shipper”) provides information to the System concerning theparticular parcel that the Seller will be selling/auctioning andsubsequently shipping. The Seller also describes to the System theSeller's rules by which potential and actual buyers (sometimes referredto herein as “Buyers/Recipients”, or simply as “Buyers”, or as“Recipients”) view the shipping, payment and other options.

A potential Buyer of an item to be purchased from a particular Seller isprompted by the System to initially provide certain limited shippinginformation (such as a destination zip code) in order to previewshipping rates for the item that the Buyer is considering purchasing.

An actual Buyer is prompted by the System to provide shipping detailssuch as the Buyer's destination address. If the Seller has instructedthe System to require the Buyer to pay shipping costs, the Systemprompts the Buyer to make the final selection of Carrier and Service.

The System in the exemplary eCommerce embodiment provides acommunication link between the Buyer and the Seller, sending certaintypes of notifications and information between them.

Further differences between the exemplary eCommerce embodiment and theexemplary simplified Internet embodiment include, among other things,the typical access entry into the System. In the exemplary simplifiedInternet embodiment, the Shipper accesses the Shipping site directly. Inthe exemplary eCommerce embodiment, the Seller/Shipper can additionally“link” to the Shipping site from the relevant eCommerce Provider's Site.

The System and screen flows for the exemplary simplified Internet andeCommerce embodiments differ somewhat. A description of the featuresthat are common between the two types of embodiments of the presentinvention is provided below as is a description of the differencesbetween the two types of exemplary embodiments.

In the exemplary eCommerce embodiment described below, the presentinvention is provided as a web-based application service from a commonprovider, sometimes referred to herein as “iShip.com”. As such, therelevant eCommerce Provider does not have to install or manage anyserver software; the Provider only provides a “link” to the System website.

B. SYSTEM OVERVIEW 1. Entity Interface Relationships

FIG. 1 is a graphic representation depicting the interface relationshipsprovided by an exemplary eCommerce embodiment of the System 1 of thepresent invention between electronic Commerce providers 2 a-2 n,Sellers/Shippers 3 a-3 n, Carriers 4 a-4 n, and Buyers/Recipients 5 a-5n. As conceptually depicted in FIG. 1, each Seller/Shipper 3 a-3 n viewsthe System 1 as an individualized automated Shipping System.

It should be noted that the use of suffixes such as “a” through “n” inconnection with numbered elements of the FIGURES herein are exemplaryand are not a limitation of the invention to any particular number.Rather, the suffixes “a” through “n” and “a” through “z”, and similarnotations, are used to represent any, but unknown, number of similarelements.

FIG. 2 depicts the interface relationships provided by an exemplarysimplified Internet embodiment of the System between the Shippers 3 a-3n, Carriers 4 a-4 n, and Recipients 5 a-5 n. As conceptually depicted inFIG. 2, each Shipper 3 a-3 n views the System 1 as an individualizedautomated Shipping System.

In both the exemplary eCommerce and simplified Internet embodiments, theSystem 1 provides Shippers/Users 3 a-3 n with a computerized shippingand tracking system that allows shipment by the same Shipper/User 3 a-3n of different packages using different services provided by differentCarriers 4 a-4 n. Carriers 4 a-4 n supported by the System includeCarriers such as Airborne, FedEx, United Parcel Service, USPS, andYellow Freight. The System 1 is completely expandable and scalable toinclude additional Carriers.

2. System Configuration and Architecture

In both the exemplary eCommerce and simplified Internet embodiments, asdepicted in FIG. 3, each User 7 (Shipper/Seller or Buyer/Bidder) hasaccess to a computer 8, for instance a personal computer (“PC”). Thecomputer 8 is configured with a display device 9 that provides a displayscreen 10. The computer 8 is further configured with one or more userinput devices, such as, for example, a keyboard 11 and a mouse 12. Thecomputer 8 is also configured with a printing device 13, such as a laserprinter. The computer 8 may also be configured with a scale 1024 and abar code reader 1027.

Users access 1003 and browse the Internet 15 using a web browser 14 thatgenerally resides and is executed on the user's PC 8. The web browser 14is a computer program or set of computer instructions that allows theShipper/User 7 to retrieve and render hyper-media content from one ormore Server computers, e.g., 20 a-21 z available over the Web. Suitablecommercially available web browsers include, e.g., Netscape's Navigator™(also sometimes referred to herein as “NETSCAPE NAVIGATOR” or simply as“Netscape Navigator”) and Microsoft Internet Explorer™ (also sometimesreferred to herein as “MICROSOFT INTERNET EXPLORER” or simply as“Microsoft Internet Explorer”).

FIG. 4 is a simplified schematic diagram of a user's computer and theinterface between the user's computer and the System servers, such as 20a-21 z in FIG. 3, using the Internet in an exemplary embodiment of theinvention in an Internet environment. PCs 8 a-8 n are used by theShippers and are connected to the Internet 15 through communicationlinks 1003 a-1003 n respectively. Optionally, a local network 1004 mayserve as the connection between some of the PCs 8 a-8 n, such as the PC8 a, and the Internet 15. Servers 20 a-21 z are also connected to theInternet 15 through respective communication links.

Continuing with FIG. 4, each of the PCs 8 a-8 n includes a centralprocessing unit (“CPU”) 1020 a for processing and managing data; userinput devices such as a keyboard 11 a and a mouse 12 a for inputtingdata and a main memory 1023 a such as a Random Access Memory (“RAM”).Information in text, graphic and other forms is displayed on the displaymonitor (“CRT”) 9 a under the control of the CPU 1020 a. A communicationdevice 1028 a, such as a modem, provides access 1003 a to the Internet15. In some embodiments, one or more Input/Output (“I/O”) devices, suchas a printer 13 a, scale 1024 a, or a bar code reader 1027 a areconfigured with the PC.

FIG. 5 is a graphic representation of an exemplary configuration of theSystem in an exemplary eCommerce embodiment of the invention depictinginterfaces with Carriers through Carrier Servers, e.g., 23-2 through27-2, and Shippers/Users through User Input, e.g., 18. When aShipper/User ships a package using the System 1, one or more of theSystem's Servers, e.g., 21 a-21 n, create a new System tracking number19. When a new System tracking number is created, one of the System'sDatabase Servers, e.g., 20 a-20 n, adds a new package record with thenewly created System tracking number to a Package Table 28. The PackageTable 28 resides in the System database 22 and contains package recordsfor System processed packages. The System database may be stored on anystorage medium, such as but not limited to, RAM, hard drive, disk drive,tape drive, or other memory device. An exemplary embodiment of thePackage Table contains the following information: 1) Package TrackingState ID; 2) Package Shipping State ID; 3) Actual Delivery Time; 4)Delivered To information; 5) Shipping Date; 6) Carrier Tracking Number;7) System Tracking Number; 8) Carrier ID; 9) Actual Package Weight; 10)Service Description; and 11) Package OID. The content of these fieldsare described further below.

As depicted in FIG. 5, using the Carrier's Internet URL, the System 1(labeled “iShip.com” in FIG. 5) then makes an HTTP (HyperText TransferProtocol) connection over the Internet 15 to the Carrier's web server,e.g., 23-2, 24-2, 25-2, 26-2, or 27-2, using the URL information for theparticular Carrier's web server.

The World Wide Web (WWW or Web) is an access protocol for HTTP(HyperText Transfer Protocol is the communication protocol used by theInternet). The unique identifier for a Server computer is called the IP(Internet Protocol) address; the unique identifier for a web site (webpage) is called the URL (Uniform Resource Locator). A URL indicates,among other things, where the Server is located, the location of the website on the Server, the name of the web page and the file type of eachdocument.

Depending upon the Carrier, the System's 1 request and report interfacewith the Carrier's web server is programmed in HyperText Markup Language(“HTML”) (e.g., 24-1, 25-1, 27-1), Extensible Markup Language (“XML”)(e.g., 26-1), or both HTML and XML (e.g., 23-1), described by way ofexample. Examples of XML formatted requests and responses with respectto Carrier interface communications are described below in connectionwith, and depicted in, FIGS. 66 and 67.

While the Shipper's/Seller's PC is connected to the Internet 15, aShipper/Seller may enter the System's 1 Internet interface in one ofseveral ways. The two principle ways discussed herein and describedbelow are: 1) by entering an Internet address, e.g., URL, to theSystem's home page; or 2) by clicking on an HTML link in aneCommerce/eAuction provider's Web site that contains the URL address toone of the System's Internet pages, for instance, an initial Userregistration page. A User may enter the System 1 in other ways, amongwhich include a direct communication interface between the User'scomputer system and the System 1.

FIG. 6 is a graphic representation depicting an alternate view of theSystem comprising the System Data Center's Server Computers 20 a-20 nand 21 a-21 z, the System Database 22, and the System's interfaces withSeller and Buyer computers 8 a-8 n, Carrier Server computers 23-2through 27-2, and eCommerce/eAuction Providers 28 a-28 n, via theInternet 15.

FIG. 7 is a simplified graphic representation of an exemplaryconfiguration of the System, and relationships between the System andCarriers and Shippers/Users, in an exemplary simplified Internetembodiment of the invention. As depicted in FIG. 7, multiple servers 20a-21 z are provided in a Network Operations Center (“NOC”). At least oneof the Servers 20 a-21 z can handle multiple telecommunicationsconnections such as over the Internet 15 at one time. In the embodimentof the NOC depicted in FIG. 7, one Server 20 a provides the computerresources to perform Proxy & Firewall functions between the Internet 15and the NOC; one Server, e.g., 21 n provides the computer resources toact as the NOC Client Server; one Server, e.g., 21 s provides thecomputer resources to act as the Tracking Server to obtain Carriertracking information 1019 from the respective carrier's to provide toShippers over the Internet 15; one Server, e.g., 20 a provides thecomputer resources to act as the Database Server to access data from oneor more databases 22 of information; one Server, e.g., 21 t provides thecomputer resources to act as the Shipping, Server; one Server, e.g., 21m provides the computer resources to act as the Web Server; and oneServer, e.g., 21 z provides the resources to provide other services,such as the upload of manifest data 1018 to the Carrier Host Systems,23-2 through 23-7.

It should be understood that the overview configurations of the Systemdepicted in FIGS. 5, 6 and 7 are exemplary. For example, the depictionof Server 20 a in FIG. 7 as having access to one or more databases 22 isnot a limitation of the invention; in alternative embodiments, such asdepicted in FIG. 5, any or all of the Servers, 20 a-20 n, have access todatabases and external storage medium.

Continuing with FIG. 7, the Servers 20 a-21 z are connected to orotherwise capable of communicating through, a communications networksuch as a global communications network such as the Internet 15, whichis in turn connected to, or capable of communicating with one or morePersonal Computers (“PC”) or other like devices, e.g. 8 a, 8 b, . . . 8n.

Continuing with FIG. 7, Users access and browse the Web using a webbrowser that generally resides and is executed on the user's PC, e.g., 8a, 8 b, 8 c . . . 8 n (and as were depicted in FIG. 4).

The Internet works based on a client/server model. The present inventionuses the client/server model to support the communication with andprocessing for each of multiple Shippers. For example, as depicted inFIG. 7, the Servers 20 a-21 z are the server side of the client/servermodel; each Shipper's PC 8 a, 8 b, . . . 8 n is a client. The presentinvention uses the web browser with which each Shipper's PC accesses theInternet to perform certain functions as further described herein.

Web sites are locations on Servers, such as one or more of the Servers,20 a-21 z, that are accessible through the Internet 15. The Servers 20a-21 z host one or more web sites which are accessible by Shipper userswith PCs (e.g., 8 a, 8 b, . . . 8 n) connected with the Internet 15.

Carrier Rules, Shipper account information and other content is storedby the Servers, e.g., 20 a in databases e.g. 22. Shippers with PCs(e.g., 8 a, 8 b, . . . 8 n) connected to the Internet 15 access CarrierRules, Shipper account information and other content that is stored bythe Servers, e.g., 20 a in databases e.g. 22 through a User Interface,which is described in detail below.

An overview of an exemplary System architecture is depicted in FIG. 8.The overview depicted is exemplary and meant to be illustrative; it isnot a limitation of the invention. As depicted in FIG. 8, one embodimentof the invention uses a three-tiered architecture.

The Data Management Tier 1201 is comprised of a Database Storagecomponent 1202 that in the embodiment depicted uses an SQL Server; aMessage Queue Storage component 1203 that in the embodiment depicteduses MS Message Queue; and a File Storage component 1204 that in theembodiment depicted uses NTFS, and DFS. Each of the Database Storagecomponent 1202, the Message Queue Storage component 1203, and the FileStorage component 1204, communicate with the Component Tier 1208 of theSystem architecture, communications by each component with the ComponentTier 1208 represented by elements 1205, 1206 and 1207 respectively.According to the embodiment depicted in FIG. 8, the Server Components ofthe Component Tier 1208 use C++ programming language and COM Objects.

The Application Tier 1212 of the System Architecture is comprised of aWeb Shipper Client component 1213 (which uses HTML, ASP and JavaScript),the NOC Administration component 1214 (which uses HTML, ASP, VB, andC++), and the Web Shipping Station component 1215 (which uses HTML, ASP,JavaScript, C++, and ActiveX Controls). Each of the Web Shipper Clientcomponent 1213, the NOC Administration component 1214, and the WebShipping Station component 1215 communicate with the Server Componentsof the Component Tier 1208 as represented by the communication elements1209, 1210 and 1211 respectively.

In one embodiment, the System is implemented in an NT environment. Thedescription of the System as being implemented in an NT environment isexemplary and is not a limitation of the invention.

3. Menu Architecture

In both the exemplary eCommerce and simplified Internet embodiments, aUser can enter the System by entering an Internet address, e.g., a URL,to the System's home page using the User's client web browser.

FIG. 9 is a graphic representation of an exemplary menu architecture aswould be displayed on an exemplary home page in an exemplary eCommerceembodiment of the System 1 as viewed by the User on a display device,e.g., 9 and 10 as depicted in FIGS. 3 and 9 a as depicted in FIG. 4,connected to the User's Computer, e.g., 8 as depicted in FIGS. 3 and 8 aas depicted in FIG. 4. The term display as used herein will beunderstood by those with ordinary skill in the art to include visualdisplay on a display device, e.g., 9 and 10 as depicted in FIGS. 3 and 9a as depicted in FIG. 4, connected to the User's Computer, e.g., 8 asdepicted in FIGS. 3 and 8 a as depicted in FIG. 4.

Other menu configurations and descriptions can be implemented withoutdeparting from the spirit of the invention. As depicted in FIG. 9, amain menu bar 34 presents several selection options, including Home 30a, Sell It 31 a, Ship It 32 a, and Track It 33 a. If a User selects,such as by using a keyboard device 11 as shown in FIG. 3, 11 a as shownin FIG. 4, or a mouse device 12 as shown in FIG. 3, 12 a as shown inFIG. 4, the Home 30 a option, the System 1 will display a Home submenu30 b.

References to a User selecting will be understood by those withreasonable skill in the art to include selection using a user inputdevice, such as a keyboard device 11 as shown in FIG. 3, 11 a as shownin FIG. 4, or a mouse device 12 as shown in FIG. 3, 12 a as shown inFIG. 4, connected to the User's Computer, e.g., 8 as depicted in FIGS. 3and 8 a as depicted in FIG. 4.

Using the exemplary menu architecture depicted in FIG. 9, if the Userselects the Sell It 31 a option, the System 1 will display a Sell Itsubmenu 31 b. If the User selects the Ship It option, the System 1 willdisplay a Ship It submenu 32 b. If the User selects the Track It 33 aoption, the System 1 will display a Track It submenu 33 b.

In an exemplary simplified Internet embodiment of the invention, theMain Menu would not provide a Sell It 31 a application or the submenusand screens associated with the Sell It 31 a application.

C. THE SELLER'S EXPERIENCE

In an exemplary eCommerce embodiment of the System, if the User entersthe System through a link from a Provider, the System 1 will ask theUser to log in. (A User that is a Buyer/Bidder that enters the Systemwith a particular Buyer/Bidder URL (Universal Resource Locator), such asthrough a hypertext e-mail link as is discussed below, is not requiredto follow the log in procedure.) The log in and registration processesdescribed below are also provided in a similar manner by some simplifiedInternet embodiments.

When a User attempts to log in, the System 1 will attempt to validatethe User's log in identification and password. If the User's log in issuccessful, the System 1 will prompt the User to select one of theavailable menu options. Otherwise, the System 1 will prompt the User toregister and will display the first of several information collectionscreens to prompt the User through the registration process. Followingis a description of the registration User Interface and the associatedSystem 1 processing in an exemplary eCommerce embodiment of theinvention.

FIGS. 10A through 10E are high level logic flow diagrams depicting thelogic flow for processing both Shipper/Seller and Buyer/Bidderinformation in an exemplary eCommerce embodiment of the invention. Anoverview of FIGS. 10A through 10E is provided immediately below forcontext. However, the detailed description of FIGS. 10A through 10E isprovided in conjunction with the detailed user interface screensdepicted in summary on FIGS. 10A through 10E. Accordingly, thedescription of FIGS. 10A through 10E is provided gradually below withintervening descriptions of the details concerning the user interfacescreens described in more detailed FIGURES that are also describedbelow.

FIG. 10A depicts general Seller/Shipper/User registration procedures.FIG. 10B depicts eCommerce/eAuction Seller registration procedures,including the Creation of a Link that the Seller can copy and paste inthe Seller's Web page description of the item to be sold/shipped. FIG.10C depicts the actual sales of the item to be shipped and depicts theBuyer 80 experience of viewing the shipping rates and times comparisonprovided by the System and purchasing or bidding on the item as the casemay be. FIG. 10D depicts the collection of shipping and paymentinformation by the Seller and the System 1 from the Buyer 80. FIG. 10Edepicts post sale shipment and payment processing, tracking andnotification. The components of each of FIGS. 10A through 10E arediscussed in detail below.

FIG. 10A depicts general User registration procedures. As depicted inFIG. 10A, the System 1 displays a registration introduction screen 41 toprompt a new eCommerce/eAuction Seller 40 to register with the System 1.

FIG. 11 is a graphic representation depicting an exemplary embodiment ofa registration introduction screen 41 depicted in FIG. 10A. As depictedin FIG. 11, the registration introduction screen 41 displaysintroductory text 101 that prompts the User to proceed to the Nextscreen to provide certain information, such as the User's e-mail andreturn address and to identify the Carriers with which the User wishesto ship. The User is instructed to press the Next button 102 if the Useris ready to proceed with registration. It will be understood by thosewith ordinary skill in the art that a User “presses” or “clicks” anonscreen button by using a user input device, such as a keyboard device11 as shown in FIG. 3, 11 a as shown in FIG. 4, or a mouse device 12 asshown in FIG. 3, 12 a as shown in FIG. 4, connected to the User'sComputer, e.g., 8 as depicted in FIGS. 3 and 8 a as depicted in FIG. 4.

Alternatively, the User can “press”, or “click”, on the Reset button 103which, when clicked, re-initializes the registration application andreturns the User to the Introduction page; the Cancel button 104, whichwhen clicked returns the User to the Logged Off Home page; or the Helpbutton 105, which when clicked, displays contextual help text in apop-up window.

If the User clicks on Next button 102, if the User is using a browserthat is not supported by the System 1, the System 1 prevents the Userfrom continuing and displays a message to the User that the User'sbrowser is unsupported. Otherwise, if the User clicks the Next button102, the System 1 will display the next screen 42 in the registrationprocess as depicted in FIG. 10A, which is a User address collectionscreen.

FIG. 12 is a graphic representation depicting an exemplary embodiment ofa User address collection screen. As depicted in FIG. 12, the Systemprompts the User to provide the User's name 106, e-mail address 107,company name 108, street address 109, floor/room number 110, departmentname 111, city 112, state 113 a (using a pull down menu button 113 b),telephone number 114, zip code 115, and fax number 116. As with theprevious registration introduction screen 41, the Next 102, Reset 103,Cancel 104, and Help 105 buttons are provided with results similar innature to the operations of these respective buttons as described above.In addition, a Back button 117 is provided. If the User clicks the Backbutton 117, the System returns the User to the screen from which theUser entered the present screen, in this case, the registrationinformation screen 41. If the User clicks the Next button 102, theSystem performs validation edits on the data entered. If any requiredfields have not been completed, or if any fields contain data found tobe in error, the System notifies the User and requests that correcteddata be entered. Because of the similar nature from screen to screen inthe System with which the Back 117, Next 102, Reset 103, Cancel 104 andHelp 105 buttons operate, the operation of these buttons will not befurther described.

If the data entered is successfully validated, the System displays thenext screen, which in this case is the Shipping Location screen 43 asdepicted in FIG. 10A. FIG. 13 is a graphic representation of anexemplary embodiment of a Shipping Location screen 43. In the ShippingLocation screen 43, the System prompts the User to identify a defaultlocation 120 a from which the User will typically ship packages and toprovide the city 122, state 123 a-123 b, and zip code 124 of thatlocation 120 b. The Shipping Location screen provides a shippinglocation input field 121 a and a shipping location pull down menu button121 b. If the user clicks on the shipping location pull down menu button121 b, the System will display a selection menu of possible shippinglocations. Example shipping location selection options include:self-service center/drop box; staffed shipping counter; my location bycalling for pickup; my location through regular pickup; and my localMail Boxes Etc. center. Exemplary shipping location options aredescribed further below with regard to FIG. 26.

If the User selects the “my local Mail Boxes Etc. center” then aLocations screen is displayed. FIG. 14 is a graphic representationdepicting an exemplary embodiment of a Locations screen. The Locationsscreen displays a Locations button 126, that when clicked, causes theSystem to display a list 127 of Mail Boxes Etc. centers in the area inand around the User's zip code. Each entry in the list 127 contains thename and address of the location 128, pickup times 129, and comments130. The User will be asked to highlight and thereby select one of thecenters. According to the User's selection, the System will displayadditional comments if appropriate, e.g., 131. Otherwise, for the othershipping location selection options, the User is required to enter thecity, state, and zip code of the location.

FIG. 15 depicts an alternative exemplary embodiment of a Locationsscreen as a screen inset. If the Shipper selects a particular “shipcenter” type from a shipping location pull down menu (not shown) as theshipping location, the User Interface will display, as shown in FIG. 15,three elements: 1) a table 1058 with the Location Address, Pickup Timesand Comments Area; 2) a Browse button 1059; and 3) a destination ZipCode field 1042. Clicking the Browse button 1059 will display additionalDrop Off Locations in a Pop-up window (not shown).

Returning to FIG. 14, if the User clicks the Next button 102, and if thedata entered in the Shipping Locations screen is successfully validated,the System displays the next screen, which in this case is the UPSregistration screen 44 as depicted in FIG. 10A. FIG. 16 is a graphicrepresentation of an exemplary embodiment of a UPS registration screen44. If the User indicates that the User will ship through the Systemusing UPS and that the User already has a UPS account 140, the User willbe asked to provide the UPS account number 141 and the scheduled pickuptime 142 a, a.m. 142 b, and p.m. 142 c. The System provides the Userwith other UPS shipping options, such as dropping the UPS shipments at ashipping center such as a Mail Boxes Etc 143, or not using the Systemfor shipping UPS 144. Depending on the User's selection, the Systemprovides appropriate special circumstance notification 145 if required.

If User clicks the Next button 102, and if the data entered in the UPSregistration screen is successfully validated, the System displays thenext screen, which in this case is the eCommerce registrationintroduction screen 45 as depicted in FIG. 10A. FIG. 17 is a graphicrepresentation of an exemplary embodiment of an eCommerce registrationintroduction screen 45. The eCommerce registration introduction screen45 provides a textual description 150 of the procedure to setup sellingpreferences for eCommerce transactions.

If the user clicks the Finish button 152 on the eCommerce registrationintroduction screen 45, the System finalizes the registration process 46and sends the User to a registration complete screen 48 a as depicted inFIGS. 10A and 10B. FIG. 10B depicts eCommerce/eAuction Sellerregistration procedures, including the Creation of a Link that theSeller can copy and paste in the Seller's Web page description of theitem to be sold/shipped.

FIG. 18 is a graphic representation of a registration complete screen 48a. The System informs the User that the User is registered 153 and thatthe User's ID and password will be e-mailed to the User 154. The Systemsummarizes the registration information for the User 155 and instructsthe User 156 to click on the Close button 157 to log on to the Systemfor the first time. If the User clicks on the Close button 157 and logson to the system, a Welcome screen, e.g., 48 b as depicted in FIG. 10B,is displayed from which the User can request that a Seller's Link becreated.

If the user clicks the Continue button 151 on the eCommerce registrationintroduction screen 45, the System will display 47 the next screen,which is an eCommerce registration screen 49 as depicted in FIGS. 10Aand 10B.

FIG. 19 is a graphic representation of an exemplary embodiment of theSeller's Carrier/Service Preferences Screen 49 as depicted in FIG. 10B.With the Seller's Carrier/Service Preferences Screen 49, the Systemrequests 159 the User to identify the Carriers and the Services of eachCarrier (e.g. Overnight Air Express 161 a, Next Afternoon Service 161 band Second Day Service 161 c for Airborne Express 160; First Overnight163 a, Priority Overnight 163 b, Standard Overnight 163 c, 2 Day 163 dand Express Saver 163 e for FedEx 162; Next Day Air Early AM 165 a, NextDay Air 165 b, Next Day Air Saver 165 c, 2nd Day Air AM 165 d, 2nd DayAir 165 e, Three Day Select 165 f and Ground 165 g for UPS 164; andExpress Mail 167 a and Priority Mail 167 b for USPS 166) that the Useris willing to allow Buyers/Bidders to choose for shipping the item(s) tobe shipped. Each supported Carrier, e.g., Airborne Express 160, FedEx162, UPS 164, and USPS 166 is available for selection by the User.Further, each service offered by a particular Carrier is also availablefor User selection. For example, for Airborne Express, Overnight AirExpress 161 a, Next Afternoon Service 161 b, and Second Day Service 161c are available for User selection. The User selects a Carrier or aservice by clicking on the selection button, e.g., 160.

FIG. 20 is a graphic representation of an alternative embodiment of theSeller's Carrier/Service Preferences Screen 49. In the example depictedin FIG. 20, the User has selected all Carriers and all services for allCarriers.

If the User clicks the Next button 102 on the Seller's Carrier/ServicePreferences Screen 49, the System will display the next screen, which isSeller's Charges and Payment Preferences Screen 50 as depicted in FIG.10B. FIG. 21 is a graphic representation of an exemplary embodiment of aSeller's Charges and Payment Preferences Screen 50. The System asks theUser to select a format for presentation of shipping charges to theBuyer/Bidder 169. The User can select any one of the followingchoices: 1) the item cost includes shipping charges 170; 2) buyer paysactual shipping charges 171; or 3) buyer pays shipping plus additionalcharges 172.

If the User chooses the option that the buyer pays shipping charges plusadditional charges, then the User must select the types of additionalcharges that apply, and the value to be added: 1) add percentage ofshipping cost 173 and specify percentage 174; 2) add fixed handlingcharge 175 and specify the amount of the handling charge 176; and/or 3)add System Service Fee 177.

The System also requires that the User select at least one paymentmethod 178: Visa 179 a, American Express 179 b, Personal Check 179 c,Cashier's Check 179 d, MasterCard 179 e, Discover 179 f, and/or MoneyOrder 179 g. The User is also given the option of requesting that theSystem collect credit card information and provide the information tothe User so that the User can process the information 180.

If the User clicks the Finish button 152 on the Seller's Charges andPayment Preferences Screen 50, then the System will display theRegistration Completion Screen 48 a previously described above.

FIG. 22 is a graphic representation of an alternative embodiment of theSeller's Charges and Payment Preferences Screen 50 depicting Userselections of some of the available options. If the User clicks the Savebutton 181, the System validates the information, saves the User'schoices and specifications, and completes the registration process.

Similarly, with respect to FIG. 21, if the user clicks the Finish button152 on the Seller's Charges and Payment Preferences Screen 50, theSystem finalizes the registration process and displays the registrationcomplete screen 48 a as depicted in FIG. 10B. As was previouslydescribed above, in the registration complete screen 48 a, the Systemsummarizes 9 the registration information for the User 155 and instructsthe User 156 to click on the Close button 157 to log on to the Systemfor the first time. If the User clicks on the Close button 157 and logson to the system, a Welcome screen, e.g., 48 b as depicted in FIG. 10B,is displayed from which the User can request that a Seller's Link becreated.

FIG. 23 is a System interactivity data and logic flow diagram depictingan exemplary embodiment of the Seller's eCommerce Registration process.FIG. 23 depicts the interactivity between the User's client machine(Seller's computer) 8 and the System's server computers 20 a-21 z. Alsodepicted are the data accesses to the System database 22. An arrow 230extending from the top of the diagram and pointing down towards thebottom of the figure graphically represents the passage of time.

As depicted in FIG. 23, the Seller clicks on the Pricing Preferencessubmenu option 231 (equivalent to 31 b-1 as depicted in FIG. 24 underthe Sell It option 31 a of the main menu 34 as depicted in FIG. 9). TheSystem servers 20 a-20 n then access the System database 22 to determinewhether the Seller's preferences have previously been set 232. In thecase that no preferences are found for the specified Seller 233, theSystem servers 21 a-21 z generate the signals necessary to display theCarriers and Services Screen 234 to the Seller's computer 8. The Sellerselects the Seller's preferred Carriers and Services and clicks the Nextbutton 235 returning control to the System servers 21 a-21 z. The Systemservers 21 a-21 z next generate the signals necessary to display theCharges and Payment screen 236 to the Seller's computer 8. The Sellerselects the Charges and Payment options and clicks the Save button 237.The System servers 21 a-21 z validate the Seller preference informationand the System servers 20 a-20 n store 238 the information on the Systemdatabase 22. The System servers generate the signals necessary to notifythe Seller at the Seller's computer 8 that the Seller's preferences havebeen saved 239.

There are different ways by which a User can request the System tocreate a Seller's Link. One way is for the User to enter the System'shome page, log in 48 b, e.g., as depicted in FIG. 10B, and click on theSell It 31 a, or equivalent, application on the main selection bar 34 asdepicted in FIG. 9. Another way is to click on the System logo icon asprovided in an eCommerce/eAuction Provider's web site. There are otherways that a User can enter the System. For instance, theeCommerce/eAuction Provider might provide a hyperlink to the System website.

If the User enters the System Web site, and clicks on the Sell Itselection 31 a, the System presents either a submenu such as 31 b asdepicted in FIG. 9, or displays a default first screen in the Sell Itapplication, depending on the embodiment.

If the User has not completely registered for the System and foreCommerce shipping processing, then the System prompts the User tocomplete the necessary registration process by displaying a RegistrationNeeds Completion screen 51 as depicted in FIG. 10B.

FIG. 24 is a graphic representation of a Registration Needs CompletionScreen 51. Similar to the screen depicted in FIG. 17, the Systemrequests the User to provide the necessary information by completing theinformation requested in subsequent screens 150-1. If the User clicksthe Next button 102, the System displays the Seller's Carrier/ServicePreferences Screen 49, and the Seller's Charges and Payment PreferencesScreen 50 as depicted in FIG. 10B.

Once the User has completed registration for the System and foreCommerce shipping processing, the System allows the User to select theCreate Link submenu option 31 b-2 in the Sell It Application 31 a of theSystem. If the User selects the Create Link option 31 b-2, the Systemdisplays a Create a Seller's Link Screen 52 as depicted in FIG. 10B.FIG. 25 is a graphic representation of an exemplary embodiment of aCreate a Seller's Link Screen 52.

Before the System can create a Seller's link, the User must tell theSystem information about the particular package that will be shipped.Accordingly, as depicted in FIG. 25, the System asks the User to enterthe shipping weight and value of the item to be shipped 190. The User isasked to enter the Shipping Weight 191 a.

FIG. 26 depicts an exemplary alternative embodiment of a screen for theinput of Shipper Parcel Specifications, which in the exemplaryalternative embodiment depicted is titled the Location and PackageScreen. The Location and Package Screen depicted in FIG. 26 collectsShipper input similar to a portion of the information that which wasdescribed in connection with FIGS. 13 and 25.

As shown in FIG. 26, the Shipper is asked to input the location 1040from which the parcel will be shipped. A pull down menu activationmechanism 1041 is provided to allow the user to pull down a menu (notshown) of different shipping locations. It should be noted that theexemplary selection mechanisms, e.g., “pull down menu”, “drop downselection”, and others, described herein are used for illustrativepurposes and are not a limitation of the invention.

The Shipper activates the pull down menu by placing the cursor of theShipper's PC over the pull down menu activation mechanism 1041 andleaving the cursor in the same position for a certain period of time(this method of activating a selection mechanism will be referred toherein as a “Pause Activation”). In alternative embodiments, the Shipperactivates the pull down menu by placing the cursor of the Shipper's PCover the pull down menu activation mechanism 1041 and clicking theShipper's user input device (this method of activating a selectionmechanism will be referred to herein as a “Click Activation”). It shouldbe understood that for each activation mechanism depicted in the UserInterface of the Present Invention, that the exemplary embodiments ofthe User Interface depicted herein use the Pause Activation method;alternative embodiments use the Click Activation method.

References herein to “clicking” mean that the Shipper places the cursorof the Shipper's PC on the subject item and clicks the Shipper's userinput device.

If the Shipper activates the pull down menu activation mechanism 1041, amenu of different shipping locations (not shown) appears in the Locationarea 1074 of the screen. The Shipper then selects one of the shippinglocations by placing the cursor of the Shipper's PC over a particularshipping location in the shipping location menu and clicking theShipper's user input device, e.g., mouse.

It should be understood that for each selection mechanism depicted inthe exemplary embodiments of the invention, selection of a particularchoice from such a selection menu is made by the Shipper clicking theShipper's user input device.

There are two types of shipping locations, ship centers and customerdrop offs. Ship centers are those locations which refer to a database ofspecific locations, from which a specific location from the availablelocations must be selected to determine rates, such as an “iShipCenter”. Customer drop offs are those shipping locations from which aspecific location need not be selected to determine rates, such as a“drop box”, “carrier counter” or “call for pickup”. The shippinglocation pull down menu displays each shipping location category, e.g.,iShip Center, other specific shipping center types, drop box, carriercounter, call for pickup, etc.

As was described with regard to FIG. 15 above, if the Shipper selects aparticular “ship center” type from the shipping location pull down menu(not shown) as the shipping location, the User Interface will display,as shown in FIG. 15, three elements: 1) a table 1058 with the LocationAddress, Pickup Times and Comments Area; 2) a Browse button 1059; and 3)a destination Zip Code field 1042. Clicking the Browse button 1059 willdisplay additional Drop Off Locations in a Pop-up window (not shown).

Returning to FIG. 26, if the Shipper selects a “customer drop off” asthe shipping location, the User Interface will display, as shown in FIG.26, two elements: 1) Origin Zip Code Field 1053; and 2) Destination ZipCode Field 1042.

For either class of shipping location, if an iShip Shipping Station willnot be present at the selected shipping location, the System displays anotice (not shown) to the customer telling them that they must have alaser printer to ship using the specified location.

If the Shipper is Logged On to the System and has established anaccount, the System will default the Shipping Location to the Shipper'sspecified Preferences which the Shipper inputs (not shown) the firsttime that the Shipper logs into the System. If the Shipper's specifiedPreference is a “customer drop off” location, the System populates theOrigin Zip Code with the Shipper's default Zip Code which the Shipperinputs (not shown) the first time that the Shipper logs into the System.

If no location is selected by the Shipper, the System displays a message(not shown) asking the Shipper to select a shipping location.

In the Package area 1075 of the screen depicted in FIG. 26 there are thefollowing controls or control groups: 1) “Packaging” which includesvarious types of parcel packaging, as shown in item numbers 1043-1047and includes Length 1048, Width 1050 and Height 1049 which are requireddata fields for parcels designated by the Shipper as the type “OtherPackaging”; 2) Weight 1051 (If the Shipper specifies one of therecognized carrier packaging types (Letter, Pak, Box, Tube) the fieldwill be auto filled with “letter”, “pak”, etc.); and 3) additionalhandling 1052. If “Letter” is selected the weight will be set by theSystem to 0.5 lbs. Otherwise, weight may be input by the Shipper (612,FIG. 27A) using a user input device such as a keyboard, with weightsranging from 1 to 150 lbs. If a specific weight is selected or input,the Packaging Type will be set to Carrier Box.

In order to identify the weight of the parcel to the System, in oneembodiment of the invention, the Shipper's PC is configured with a scaleand the System communicates with the Shipper's scale using the user'sclient web browser. FIGS. 27A through 27C depict the logic flow forcommunications between the System and a Shipper's PC and a scaleconfigured with the Shipper's PC. As depicted in FIGS. 27A through 27C,the Shipper establishes in the System certain information about theShipper's PC configuration at the time the Shipper sets up an Account601. If the Shipper's PC is configured with a scale, the Shipperspecifies scale configuration information 602 such as: the make andmodel of scale, and the type of port (e.g., serial or parallel) withwhich the scale is configured with the PC. Further, the System providesstorage and access 603 for the Shipper's scale configuration informationin a database 604.

Continuing with FIGS. 27A through 27C, the System supports various makesand models of scales. Each scale make and model has a set of featuresand requirements for which the System must be programmed in order forthe System to communicate properly with each particular scale. TheSystem provides an ActiveX control dedicated to communications withperipheral devices configured with client PCs (“Shipping Station ActiveXControl”) 607. Contained within the Shipping Station ActiveX Control isa table (the “scale table”) 608 containing entries for each supportedscale make and model and provides logic to process the communicationinformation for each scale make and model as appropriate. It should beunderstood by someone skilled in the art that the Shipping StationActiveX Control facilitates communications with various devices on theclient machine. The Shipping Station ActiveX Control 607 and the scaletable 608 are requested 606 by the web page (the “System/scaleinterface”) containing the Weight field 1051 at the time that theShipper activates 605 the Weight field 1051. Once the web page requeststhe Shipping Station ActiveX Control 607, the Shipping Station ActiveXControl 607 is automatically installed on the client 609. In the eventthat the Shipping Station ActiveX Control is updated to facilitate thesupport of additional scale makes and models, the Shipping StationActiveX Control is automatically reinstalled on the particular client PCthe next time that the Shipper activates the Shipping Station ActiveXControl.

Continuing with FIGS. 27A through 27C, the Shipper places 610 theSubject Parcel on the scale, such as, e.g., the scale 1024 a depicted inFIG. 4, and 1024 n depicted in FIG. 7. The Shipper activates theShipping Station ActiveX Control by placing the cursor of the Shipper'sPC on the Weight field 1051 (such as the Weight field 1051 depicted inFIGS. 15 and 26). The System checks the Shipper's scale configurationinformation to determine 611 whether the Shipper's PC is configured witha scale. If so, the System activates the System/scale interface 613.Otherwise, the user may input the weight 612 in the Weight field 1051 asdepicted in e.g., FIG. 26.

In one embodiment of the System/scale interface aspect of the invention,the System uses ActiveX control language and the client's web browser,such as Internet Explorer browser. Continuing with FIGS. 27A through27C, using the Shipper's scale configuration information, the Systemcalls Windows libraries 615 to open the serial or parallel port withwhich the scale is configured, as the case may be and as is specified inthe Shipper's scale configuration information. Windows is an operatingsystem used with most PCs.

Continuing with FIGS. 27A through 27C, the System uses the informationfor the particular scale make and model from the scale table 608 ofscale makes and models to send a communication query to the particularscale 616. Typically, the communication query information required by aparticular scale make and model is a particular set of characters. Eachscale make and model recognizes a unique set of characters as a requestfor a weight. Accordingly, the appropriate set of characters that meansa request for weight to a particular scale make and model is stored inthe scale table for a particular scale make and model.

Continuing with FIGS. 27A through 27C, after a proper query, a scalewill return a data stream containing the weight of the parcel 617.Depending on the scale make and model, other types of information may becontained in the return data stream. The System accesses the scale table608 to interpret 618 the return data stream according to the scale makeand model rules as stored in the scale table and as programmed in theShipping Station ActiveX Control.

Other scale communication information is contained in the scale tablefor each scale make and model, including, for example: the characterstring that communicates a request as to whether or not the weight isstabilized; the default contents of the return data stream of the weightfrom a particular scale make and model; and the character string torequest that the scale send the weight mode with the return data stream.Weight mode is the mode with which the scale measures weight (e.g.,pounds, kilograms, etc.).

In one embodiment, if no weight difference is determined, as long as theShipper's cursor remains on the Weight field 1051 (such as the Weightfield 1051 depicted in FIGS. 15 and 26), the System polls the scalerepeatedly requesting the weight and requesting notification that theweight is stabilized 619. Each time the System polls the scale, theSystem tests to determine 620 whether or not there is a difference inthe weight as compared with the last time that the System polled thescale. If the System determines a difference in weight, then the Systemuses the Shipping Station ActiveX Control to fire an event 621 to theclient web browser to display on the User Interface screen that theweight has changed.

In one embodiment, once the Shipper removes the cursor from the Weightfield 1051, the System stops polling the scale 622. If prior to the lastpolling to the scale, the scale notifies the System that the weight hasstabilized 623, the System will proceed with preparing the Graphic Arrayif requested to do so by the Shipper 625. Otherwise, if the Systemdetermines a difference in weight, the System notifies the Shipper thatthe weight is not stable 624.

The Shipper can use the Shipper's input device connected to theShipper's PC, such as a mouse 12 a, as depicted in FIG. 4, to positionthe cursor on one of the navigational buttons 102-105 shown at thebottom of the screen as depicted in FIG. 26 described above. If theShipper clicks the “Next” button 102, the System will display the nextScreen, which, in the embodiment depicted, is the Rates and Times Screen(an exemplary embodiment of which is depicted in FIG. 36A describedbelow). If the Shipper clicks the “Reset” button 103, the System willclear the values displayed on the current screen. If the Shipper clicksthe “Cancel” button 104, the System will cancel the Shipper's ParcelSpecifications and the Shipper's service request. If the Shipper clicksthe “Help” button 105, the System will display help text to explain tothe Shipper the appropriate possible actions.

Returning to FIG. 25, Shipping Weight can be input by clicking theShipping Weight pull down menu button 191 b which will cause a displayof commonly selected weights, such as “Letter—0.5 lbs” and weights from1 to 150 lbs. Alternatively, in one exemplary embodiment, the Userinputs the weight of the package by placing the actual package on ascale that is configured with the User's computer and with which theSystem is programmed to interact as disclosed above.

The User is also asked to identify whether the item is irregular orrequires non-standard packaging 192. Regarding Loss Protection, thedefault is Basic Coverage 193. If the User instead selects DeclaredValue 194, the User is required to enter a value 195 greater than $0.00and less than or equal to $50,000.00.

Once the User has entered the package specific information 191 a-195, asdescribed above, the User can request the System to preview the shippingcharges that will be presented to a Buyer/Bidder. To do so, the User mayeither: 1) choose an example destination 196 a and uses the destinationpull down menu button 196 c to select a sample destination city 196 bfrom a list of cities; or 2) choose to enter an example zip code 197 aby entering a sample zip code 197 b. Then the user clicks the Previewbutton 198 to display the sample charges. If a sample destination citywas selected from the pull down list of cities, once the User clicks thePreview button 198, the System identifies the appropriate zip code forthe selected city and moves that zip code into the Destination Zip codefield 197 b.

FIG. 28 depicts an exemplary further supplemental Shipper ParcelSpecification Screen such as in a simplified Internet embodiment of theinvention, which in the embodiment depicted is titled the ServiceOptions Screen. The Service Options Screen provides for Shipper input ofService Option Selections (1076, 1077, 1078, 1083-1088) and displays aSingle Day Rate Graphic Array. The Service Options supported in thedepicted embodiment are: 1) Loss Protection (Declared Value) 1076;Delivery Notification 1077, namely 2) E-Mail Delivery Notification 1083;3) Verbal Delivery Confirmation 1085; and other options 1078, namely 4)“Service must be guaranteed” 1086; 5) “Destination is a Residence” 1087;and 6) “Signature not Required” 1088. Selection of an option on thescreen depicted in FIG. 28 is accomplished by the Shipper placing thecursor on the option selection mechanism and clicking the Shipper's userinput device.

With respect to the Loss Protection (Declared Value) Service Option, ifthe Shipper selects the Declared Value Option 1081, the Shipper mustenter a value 1082 of greater than $100.00, and equal to or less than$50,000.00. The default for Loss Protection is “Basic Coverage” 1080which provides automatic coverage for the first $100.00 of DeclaredValue If the Declared Value option 1081 is selected and a value 1082entered, the System will update the Single Day Rate Graphic Array 1096with changes for each individual Carrier's rates, e.g., 1097.

It should be noted that the Carrier Rules described herein, such as inthe case of the defaults, threshold values, and the like concerning LossProtection, are contained in the Carrier Rules database (e.g., 1404 athrough 1404 n as depicted in FIG. 38), and for special cases, areprogrammed as part of the System. Carrier Rules vary from Carrier toCarrier; Carrier Rules are subject to change. The Carrier Rulesdescribed herein are therefore not a limitation of the invention.

With respect to the E-Mail Delivery Notification Option, two controlsare provided—a checkbox 1083 and an “E-Mail Others” button 1084. If theE-Mail Delivery Notification Option checkbox 1083 is checked the rates,such as those displayed in the Single Day Rate Graphic Array 1096, willbe updated to reflect each Carrier's charges for the provision of E-MailNotification services. If Shipper clicks the “E-Mail Others” button1084, the following will occur: 1) If the checkbox 1083 has not alreadybeen checked, it will be checked by the System; and 2) an “E-MailOthers” pop-up window will be displayed by the System as depicted inFIG. 60 and described below.

With respect to the Verbal Delivery Confirmation Option, if the VerbalDelivery Confirmation Option checkbox 1085 is checked, the rates, suchas those displayed in the Single Day Rate Graphic Array 1096, will beupdated to reflect each Carrier's charges for the provision of VerbalDelivery Confirmation services. If the Verbal Delivery ConfirmationOption checkbox 1085 is checked, the System will use the Shipper'sReturn Address Phone and Name as supplied by the Shipper during Accountsetup (not shown), as the information to be supplied to UPS.

With respect to the “Service must be guaranteed” Option, if the “Servicemust be guaranteed” Option checkbox 1086 is checked, the rates andCarrier/Service cells, such as those displayed in the Single Day RateGraphic Array 1096, will be updated to remove any Carrier/Service cellfor which service is not guaranteed.

With respect to the “Destination is a Residence” Option, if the“Destination is a Residence” Option checkbox 1087 is checked, the ratesand Carrier/Service cells, such as those displayed in the Single DayRate Graphic Array 1096, will be updated to remove any Carrier/Servicecell which does not provide service to Residence Destinations.

With respect to the “Signature not Required” Option, in the embodimentdepicted in FIG. 28, if the “Signature not Required” Option checkbox1088 is checked, no change will be applied to the rate graphic. In theembodiment depicted in FIG. 28, the “Signature not Required” Option is aFedEx only flag and does not effect any other Carrier or any Carrierrate.

The Single Day Rate Graphic Array as displayed in FIG. 28 is similar tothe Graphic Array described below as depicted in FIG. 36A in that theSingle Day Rate Graphic Array is dynamically dimensioned and reflectsthe Carriers (1032-1 through 1032-7) that provide the delivery servicerequested by the Shipper for a particular Subject Parcel. As with theGraphic Array, the embodiment of the Single Day Rate Graphic Arraydepicted in FIG. 28 uses a color-coded legend 1091 and color (e.g., 1140a, 1141 a, 1142 a) to distinguish the rates for each Carrier (e.g., 1140b, 1141 b, 1142 b) from the rates for the other Carriers.

The Single Day Rate Graphic Array contains a number of elements. First,the selected delivery date 1090 is displayed at the top of Single DayRate Graphic Array. The displayed date is bordered on the left 1098 andright 1099 with arrow buttons. If the Shipper clicks the left arrowbutton 1098, the date will go back one valid delivery date. If theShipper clicks the right arrow button 1099, the date will move forwardone valid delivery date. The range of valid delivery dates is determinedby the System according to the Expected Ship Date (element 1060 asdepicted in FIG. 36A).

Sorted, valid delivery times 1093-1 through 1093-5 for all valid datesare displayed down the left side of the Single Day Rate Graphic Array.Above the delivery times are up and down arrow buttons 1101 a and 1101 brespectively. If an up or down arrow button (1101 a and 1101 brespectively) is pressed, the list of available times 1093-1 through1093-5 will scroll up or down appropriately, if and only if the listexceeds the Single Day Rate Graphic Array display area 1096.

A Ship Location Type field 1066 and Ship Location drop down menuactivator 1067, are displayed below the Single Day Rate Graphic Arrayand operate in a manner as described in FIG. 36A. If the Shipper changesthe Ship Location selection, the System will update the Single Day RateGraphic Array to reflect any rate changes or surcharges that result fromthe change.

As with the Rates and Times Screen (described below as depicted in FIG.36A), the Single Day Rate Graphic Array is color coded by Carrier in acolor-coding legend 1091—that is, a distinct color is visually depictedin a legend as corresponding to each respective Carrier. Carrier cellentries, e.g., 1097, for each Carrier are presented in a color-codeddisplay of the available rate, by date and time.

As depicted in FIG. 28, the color for the Carrier identified as“Airborne” 1140 b is depicted in the color coding legend 1091 with aright-diagonal cross-hatch symbol 1140 a. Accordingly, each Carrier cellentry, e.g., 1097, contained within the Single Day Graphic Array with aparticular distinct color, in this case depicted with the right-diagonalcross-hatch symbol 1140 a, corresponds to a delivery of the SubjectParcel supported by the Carrier “Airborne” 1140 b.

Each Carrier cell entry, e.g., 1097, contains a graphic element, e.g.,1097 a, which contains what is known as “ALT text”. A Shipper viewingthe Single Day Rate Graphic Array online can place the PC's cursor onthe graphic element, e.g., 1097 a of a particular Carrier cell entry,e.g., 1097, to display a pop-up screen (not shown) that displays the ALTtext for that particular Carrier cell entry. The ALT text containsinformation about the Carrier, as described in FIG. 36A, such as thefull Carrier name and the full Carrier service name. The contents of theALT text described herein is exemplary and is not a limitation of theinvention.

Appearing in each of each of the color-coded Carrier cell entries is amonetary value, e.g., 1097 b, of the price that the correspondingCarrier would charge to deliver the Subject Parcel according to the timeand date specified. For example, as depicted in FIG. 28, the Carriercell entry 1097, depicted with the right-diagonal cross-hatch symbol1140 a, contains the amount $9.00 (1097 b). Accordingly, the amount$9.00 (1097 b) is the price that the Carrier Airborne would charge todeliver the Subject Parcel at the identified time of 12:00 p.m. 1093-3on the identified date of Monday, Sep. 28, 1999 1090.

Similarly, as depicted in FIG. 28, the color for the Carrier identifiedas “FedEx” 1141 b is depicted in the color coding legend 1091 with aleft-diagonal cross-hatch symbol 1141 a. Accordingly, each Carrier cellentry contained within the Graphic Array with the left-diagonalcross-hatch symbol, e.g., 1107, corresponds to a delivery of the SubjectParcel supported by the Carrier “FedEx.”

Further, as depicted in FIG. 28, the color for the Carrier identified as“UPS” 1142 b is depicted in the color coding legend 1091 with a verticalcross-hatch symbol 1142 a. Accordingly, each Carrier cell entrycontained within the Graphic Array with the vertical cross-hatch symbol,e.g., 1108, corresponds to a delivery of the Subject Parcel supported bythe Carrier “UPS.”

In the embodiment of the Service Options Screen depicted in FIG. 28, thenavigational buttons operate much the same as has been previouslydescribed except that clicking the “Back” button 117 will display theprevious screen, which in the embodiment depicted is the Rates and TimesScreen (FIG. 36A); clicking the “Next” button 102 will display the nextscreen, which in the embodiment depicted is the Summary Screen (FIG.48). The Shipper must select a Carrier cell entry before the System willdisplay the Summary Screen. To select a Carrier cell entry, the Shipperplaces the cursor over the entry and clicks the user input device. In analternative embodiment, the Shipper double clicks a Carrier cell entryto select the entry. Clicking the Reset button 103 will clear all fieldsin the Service Option Screen depicted in FIG. 28 and return the displayof the Location and Package Screen (as described above with regard toFIGS. 15 and 26).

Returning to FIG. 25, once the User is satisfied with the previewedcharges, the User can create a Seller's link. To do so, the User mustchoose the type of Link, HTML 199 or Web Address only 200, enter theLink Text 201 that will be displayed, and click the Go button 202.

Once the User clicks on the “Go” button 202, the System generates anHTML hyperlink and moves the HTML hyperlink in the “Link” box 203 a. Ifthe HTML hyperlink text exceeds the space available on the Create aSeller's Link Screen, the User can click on the up and down scrollbuttons, 203 b 1 and 203 b 2 respectively.

FIG. 30 depicts an exemplary alternative embodiment of the Create aSeller's Link screen. In this embodiment, the System collects thepackage specific information when the Seller enters the System and thenpresents the screen as depicted in FIG. 30 to display the generatedhyperlink.

On the Seller's Link Screen depicted in FIG. 30, an Affiliate's Logo 215is displayed. The Affiliate's Logo 215 represents the logo of anaffiliated eCommerce/eAuction provider. When Affiliate co-branding isdesired, an affiliate identifier is appended to the end of the URL thatrefers to the Sell It application as that URL is provided in theaffiliate Provider's Web site. An affiliate identifier is an accountnumber that begins with the prefix “AFF”. When a Seller clicks on a logoor hyperlink for the System that has an affiliate identifier, theaffiliate identifier is sent to the System with the hyperlink. If theSystem receives an affiliate identifier in a hyperlink, the Systemaccesses the System database 22 as depicted in FIG. 5, retrieves theaffiliate's logo and color scheme, and uses the affiliate's logo, pageelement specifications, and color scheme to alter page elements of theSystem screens.

In one embodiment, the System generates an HTML hyperlink by executing aJAVA script routine (in alternative embodiments, other scripts areused). The JAVA routine extracts the Seller's package-specificinformation from the Create a Seller's Link HTML page (i.e., Weight,Irregular or Non-Standard Packaging, Loss Protection, Destination Zipcode, Link Type and Link Text) and integrates the information with a URL(Universal Resource Locator) that points to the address at which aSystem web page exists, or a series of System web pages exist, that willdisplay shipping cost comparisons for a Buyer/Bidder. In one embodiment,the URL information is hard coded in the web page. The hyperlink builtby the System contains data as well as an address. In an alternativeembodiment, the URL is dynamically generated.

In order to create the Link, the System places the appropriate HTML tagsand text in a sequence that can be rendered by a web browser. An exampleof a hypertext link, like the one generated in FIGS. 25 and 29, that the“Create Link” application creates is depicted in FIG. 31. Some of thetext of the Link (a hyperlink) depicted in FIG. 31 is a template.However, several components are customized according to the Seller's andthe specific item's information. For instance, the example hyperlinkdepicted in FIG. 31 contains a variable data item named “K” 210-1 whichis set equal to the account number 210-2 (“A6V1XZ” in this case) of theSeller's account 210. The example hyperlink depicted in FIG. 31 alsocontains a variable named “W” which is set equal to the weight in poundsof the package to be shipped (in this case “10”) 211; a variable named“V” set equal to the declared value for loss protection of the package(in this case “0”) 212; and a variable named “H” which is set equal toan indicator, which if set to “1”, the package has irregular ornon-standard packaging, if set to “0” (as in this case”), the package isregular with standard packaging 213.

After the System generates the HTML hyperlink, the Seller can copy theHTML hyperlink text 203 a as depicted in FIG. 30 using generallyavailable text editing features such as click, drag and copy. The Sellerthen returns to the Seller's web site or to the eCommerce/eAuctionProvider's from which the Seller entered the System and paste the Linktext in the Seller's eCommerce/eAuction item description.

The Buyer's/Bidder's experience is described in detail below. However,for purposes of describing the Seller's Link, when the Buyer/Bidderclicks on the Seller's Link in the Seller's web page, theBuyer's/Bidder's Web Browser will use the URL to locate the System Webpage that is addressed by the Link. The System will be presented withand receive as input the information in the hypertext link, includingthe variables and their respective contents as described above 210-213in connection with FIG. 31.

With the Seller's account number 210, the System accesses the Systemdatabase 22 as depicted in FIG. 5 and retrieves the following types ofinformation about the Seller: 1) Package origin address; 2) Carriers andservices that the Seller has chosen to use; 3) Custom and public carrierrates the Seller can use; 4) Additional handling charges that the Sellerwants to imposes; and 5) Payment methods the Seller will allow the buyerto use. This type of information was collected by the System during theSeller's Registration process as was described above (e.g., inconnection with FIGS. 9-14, 16-25).

With the Seller's information as collected through the Registrationprocess and with the package specific information as provided by thehyperlink Seller's Link, the System, at the address provided by the URL,is programmed to interact with the Buyer, as will be described in detailbelow, to facilitate shipping of the package, payment informationcollection, and depending upon the previously provided (during Sellerregistration) instructions of the Seller, payment processing.

FIG. 32 depicts an alternative embodiment of a hyperlink generated bythe System. Instead of the hyperlink explicitly containing the Seller'saccount number 210 and package specific information, e.g., 211-213, asdepicted in FIG. 31, the hyperlink depicted in FIG. 32 provides aPackage Identifier (“PID”) 220. A PID hides Seller account informationand package specific information from the Buyer/Bidder by replacing theexplicit embedded information with a single string of faciallymeaningless characters. In an embodiment of the System that generates aPID for each package/Seller's Link, every time a Seller creates a URLwith a PID, the System creates a new and unique PID. Without access tothe iShip database, there is no information in a PID from which todetermine a Seller's information.

The System stores the PID 220 in a PID table in the System database 22(such as depicted in FIG. 5) and stores the Seller's account and packagespecific information, e.g., 210-213 (such as depicted in FIG. 31) withthe PID.

In another embodiment, the details associated with the Seller's account,such as the Seller's various eCommerce and shipping preferences, arestored in detail with the PID 220. Storing detailed information with aPID 220 provides for additional flexibility in that new Sellerinformation can be associated with the new PID while not influencing apreviously generated PID and its associated set of information.

FIGS. 33A and 33B represent a database schema diagram that depicts anexemplary embodiment of tables in which data is stored by the Systemregarding a particular Seller Account, and from which information isretrieved in order to begin the process of presenting to theBuyer/Bidder a shipping cost multi-carrier, multi service comparisonGraphic Display, which itself will be discussed in more detail below.

As depicted in FIGS. 33A and 33B, the database schema 250 is comprisedof an Account User table 251 (comprising, e.g., 251-1, 251-2, 251-3,251-4), a Users table 252 (comprising, e.g., 252-1, 252-2, 252-3,252-4), an Account User Configuration table 253 (comprising, e.g.,253-1, 253-2, 253-3, 253-4), a Carrier Account table 254 (comprisinge.g., 254-1, 254-2, 254-3, 254-4, 254-5), an Account table 255(comprising, e.g., 255-1, 255-2, 255-3, 255-4), an Account and CarrierAccount table 256 (comprising, e.g., 256-1, 256-2, 256-3), an Addresstable 257 (comprising, e.g., 257-1, 257-2, 257-3, 257-4, 257-5, 257-6,257-7), a Site Type table 258 (comprising, e.g. 258-1, 258-2, 258-3,258-4), an Account and Site Type table 259 (comprising, e.g., 259-1,259-2), an Account and Site table 260 (comprising, e.g., 260-1, 260-2),and a Site table 270 (comprising 270-1, 270-2, 270-3). As depicted inFIGS. 33A and 33B, the Account User table 251 comprises, e.g., anaccount number (“AccountNo”) 251-1, a user ID (“UserID”) 251-2, an OIDAddress (“AddressOID”) 251-3, a date of creation (“CreateDate”) 251-4,etc. Users table 252 comprises a user ID (“UserID”) 252-1, a LogOnName252-2, a Password 252-3, an active indicator (“Active”) 252-4, etc. TheAccount User Configuration table 253 comprises, e.g., an account number(“AccountNo”) 253-1, a UserID 253-2, an Item 253-3, a Value 253-4, etc.The Carrier Account table 254 comprises a Carrier Account ID 254-1, aCarrier Account Name 254-2, a Billing Address OID 254-3, an Activeindicator 254-4, a Commissioned indicator 154-4, etc. The Account table255 comprises, e.g., an Account Number 255-1, a Mailing Address OID255-2, an Active indicator 255-3, Tracking Number information 255-4,etc. The Account and Carrier Account table 256 comprises, e.g., anAccount Number 256-1, a Carrier Account ID 256-2 and a Carrier ID 256-3.The Address table 257 comprises, e.g., an Address OID 257-1, a ContactName 257-2, an email address 257-3, a Company Name 257-4, an Address257-5, a City 257-6, a State 257-7, etc. The Site Type table 258comprises, e.g., a Site Type ID 258-1, a Site Type OID 258-2, aDescription 258-3, a Name 258-4, etc. The Account and Site Type table259 comprises an Account Number 259-1 and a Site Type ID 259-2. TheAccount and Site table 260 comprises, e.g., an Account Number 260-1 anda Site OID 260-2. The Site table 270 comprises a SiteOID 270-1, anActive indicator 270-2, and an Address OID 270-3.

The Account table 255 holds, among other things, information about eachSeller's account. In preparing the multi-carrier shipping costcomparison Graphic Display, the System accesses the Account table inorder to determine whether the Account number 210-2 contained in thehyperlink text is a valid Account number 255-1 and in an Active state255-3.

The Account User table 251 is used, among other things, to associate theSeller's account information with the Seller's security and addressinformation. An address pointer 251-3 into the Address table 257 is used257-1 to retrieve the Seller's origin address.

The Account User Configuration table 253 contains the Seller'spreference settings (not shown) as specified by the Seller. Theseinclude Seller's choice of carriers, services, payment options, type ofdrop-off/pickup option, and any handling charges the Seller wishes toimpose on the buyer.

The Address table 257 holds all the addresses that are used in Systemapplications. In addition to normal mailing address information, otheritems stored in this database table include the Seller's e-mail addressand phone numbers.

The Carrier Account table 254 holds the carrier account information thatthe System uses when a Seller ships a package. As well, this table 254contains information for generating each Seller's rates for eachcarrier.

The Account and Carrier Account table 256 ties the carrier accounts254-1 from the carrier Account table 254 to the Carrier Accounts 256-2with which the Seller has specified as a preferred Carrier to aparticular Seller's account 256-1.

The Site Table 270 contains information about drop off and pickup sitelocations. The Site Type table 258 contains information about each typeof site.

The Account and Site table 260 relates a particular Seller Account 260-1to a particular site pointer 260-2 which in turn points to a particularsite record 270-1 in the Site table 270.

The Account and Site Type table 259 relates a particular Account 259-1to a particular site type 259-2 which in turn points to a particularsite type record 258-1.

In one embodiment, once the Seller has decided upon the Seller'spreferred options, the information in the Site Type, Account and SiteType, Account and Site and Site tables 258-270 are stored in the AccountUser Configuration table 253.

Most eCommerce web sites and eAuction sites allow the Seller to generatea custom Seller's web page for each item being sold. Typically, theSeller's web page utilizes HTML for the layout, and descriptions andpictures of the item sold or auctioned. During the process ofestablishing an eCommerce/eAuction web page, the Seller utilizes theSystem to register for the System's shipping management services, toenter the Seller's preferences as described above, and to enterparameters such as, for example, the weight and packaging, lossprotection and value of the package, as described above that describethe particular item the Seller is selling/auctioning. The Seller thenuses the Create a Seller's Link function of the System to create ahyperlink. The Seller then uses customary edit controls to copy thehyperlink and paste the hyperlink into the description of the item to besold at the Seller's web site. The result is an HTML hyperlink to viewthe shipping charges from the auction item description field, anexemplary embodiment of which is depicted in FIG. 34.

As depicted in FIG. 34, the exemplary item bidding requirements andcircumstances 301 are described in the Seller's auction web site page. Adescription of the item available for bidding is provided 302. TheSeller has used the System to copy the hyperlink 203 a created by thesystem into the description 302 of the item. After returning to theSeller's auction web site page describing the particular item, theSeller used customary edit controls to paste the hyperlink into thedescription 302 of the item 303. The Seller's web site page 53 isdepicted in FIG. 10C.

D. THE BUYER'S EXPERIENCE IN AN ECOMMERCE EMBODIMENT

In an eCommerce embodiment of the present invention, the Buyer/Bidderenters the Seller's eCommerce/eAuction web site page, such as the onedepicted in FIG. 34, and reviews the Seller's description of the item tobe sold/auctioned. If the Buyer/Bidder is interested in the item, theBuyer/Bidder may click on the System hyperlink 303 for that Seller'sitem shipping charges.

If the Buyer (80, FIG. 10C) clicks on the System hyperlink 303, asdepicted in FIG. 10C, the Buyer/Bidder enters the System at the URLaddress supplied by the hyperlink. FIG. 35 is a graphic representationof an exemplary Buyer shipping rating information collection screen thatthe Buyer would see upon entry into the System. As depicted in FIG. 35,the System displays a Buyer data collection screen 55 (in FIG. 10C) tothe Buyer, instructing the Buyer to enter the Buyer's zip code and otheroptions, and to click on the Get Rates button 317 to get a comparison ofrates 310. The Buyer enters the deliver-to zip code 311, identifieswhether the delivery will be made to a business address 312 or aresidence 313, and whether yes 314 or no 315 the Buyer wants theselected Carrier/service to guarantee a delivery time. The Systeminstructs the Buyer to click the “Back” button on the Buyer's webbrowser to return to the Seller's item web site page 316.

Once the Buyer has supplied the necessary information, if the Buyerclicks the Get Rates button 317, the System validates the informationsupplied by the Buyer and then combines the information supplied by theBuyer with the information set for the Seller during the Seller'sregistration/eCommerce registration and calculates and displays amulti-carrier, multi-service rate and time shipping cost comparisonGraphic Array 56 (as depicted in FIG. 10C).

An exemplary embodiment of a multi-carrier, multi-service rate and timeshipping cost comparison Graphic Array in an exemplary simplifiedInternet embodiment of the invention is depicted in FIG. 36A.

a) The Graphic Array Display

FIG. 36A depicts an exemplary Dynamically Dimensioned Multi-Carrier,Multi-Service Graphic Array online display as part of an exemplarysupplemental Shipper Parcel Specification Input Screen. FIG. 36A depictsa Graphic Array for an exemplary simplified Internet embodiment. In theembodiment of the Graphic Array depicted in FIG. 36A, the particularscreen is titled the Rates and Times Screen.

As depicted in FIG. 36A, the exemplary Graphic Array contains thefollowing information and display elements: 1) valid delivery dates 1063(1063-1 through 1063-3) across the top of the graphic display for theselected Ship Date; 2) sorted, valid delivery times 1064 (1064-1 through1064-6) for all valid dates down the left side of the graphic display;and 3) color coded by Carrier, Carrier cell entries, e.g., 1065, foreach available rate, by date and time.

In the exemplary embodiment depicted in FIG. 36A the Graphic Arraycomprises an array of intersecting rows and columns. Each columncorresponds to a day and date of parcel delivery. In FIG. 36A, the daysand dates of delivery shown are “TUE 28 SEP 99” (1063-1), “WED 29 SEP99” (1063-2) and “THU 30 SEP 99” (1063-3). As depicted in FIG. 36A,space for other columns (1063-4 through 1063-7) are available fordisplay; in the case of the example depicted in FIG. 36A however, nodates are displayed in those columns.

Each row of the Graphic Array corresponds to a time of delivery. In FIG.36A, the times of delivery are shown as “8:00 AM” (1064-1), “10:30 AM”(1064-2), “12:00 PM” (1064-3), “3:00 PM” (1064-4), “4:30 PM” (1064-5),and “5:00 PM” (1064-6).

At the intersection of each row (1064-1 through 1064-6) and column(1063-1 through 1063-7) of the Graphic Array is a “cell.” In FIG. 36A,cells will be referred to by the element 1071, and by the intersectingrow (1 through 6) and column (1 through 7) the intersection of whichforms the space for each cell (1071-1-1, 1071-1-2, . . . 1071-6-7). Someof the cells depicted in FIG. 36A are empty, e.g., 1071-5-1, 1071-6-1,1071-6-3, 1071-6-4. Empty cells represent the circumstances that none ofthe Carriers supported by the System (the “supported Carriers”) supportdelivery of the Subject Parcel for the time and date for which that cellrepresents the intersection.

Some cells depicted in FIG. 36A have one or more cell entries. In FIG.36A, each cell entry represents a particular Carrier. Each Carrier cellentry is color coded with a unique color, the unique color correspondingto a particular Carrier as is discussed in more detail below; eachCarrier cell entry contains a graphic element, e.g., 1147 a, and amonetary amount, e.g., 1147 b, which represents the price for which thecorresponding Carrier would deliver the subject parcel. For instance,cell 1071-1-1 contains a single Carrier cell entry 1148. Cell 1071-3-1contains two Carrier cell entries 1065 and 1149.

A color-coding legend 1062 is displayed on the Screen to identify by aname (1140 b, 1141 b, 1142 b, and 1143 b) and a color-coding symbol(1140 a, 1141 a, 1142 a, and 1143 a), each of the supported Carriers(e.g., 1140, 1141, 1142, 1143) that provide the service according to theparticular Shipper's Parcel Specifications for the particular SubjectParcel.

For purposes of this application, unique colors are depicted withgraphic symbols. For example, a right-diagonal hash mark symbol 1140 ais used herein to represent the color red; a left-diagonal hash marksymbol 1141 a is used herein to represent the color purple; a verticalhash mark symbol 1142 a is used to represent the color amber; and ahorizontal hash mark symbol 1143 a is used to represent the color blue.The particular hash mark symbols used herein and the colors mentionedherein are exemplary and are not a limitation of the invention.

Each cell of the Graphic Array that is not empty contains one or morecolor-coded Carrier cell entries. For example, in FIG. 36A, cell1071-3-1 contains two Carrier cell entries, 1065 and 1149. Carrier cellentry 1065 is color-coded with the right-diagonal hash mark symbol(representing the color red) which, according to the color-coding legend1062, corresponds 1140 a with the Carrier identified as “Airborne” 1140b. Carrier cell entry 1149 is color coded with the horizontal hash marksymbol (representing the color purple) which, according to thecolor-coding legend 1062, corresponds 1143 a with the Carrier identifiedas “USPS” 1143 b.

Each Carrier cell entry, e.g., 1065, contains a graphic element, e.g.,1065 a, which contains what is known as “ALT text”. As depicted in FIG.36A, a Shipper viewing the Graphic Array online can place the PC'scursor on the graphic element, e.g., 1065 a of a particular Carrier cellentry, e.g., 1065, to display a pop-up screen 1069 that displays the ALTtext for that particular Carrier cell entry. In some embodiments, theALT text will be displayed by merely placing the cursor over the graphicelement for a particular Carrier cell entry and leaving the cursor inthat position for a certain time interval. In alternative embodiments,the Shipper must click on the graphic element for a particular Carriercell entry in order to display the ALT text. In the exemplary embodimentdepicted in FIG. 36A, the displayed ALT text, e.g., the text displayedin pop-up screen 1069, contains the full Carrier name (in the depictedcase, “Airborne Express”) and the full Carrier service name (in thedepicted case, “Express Overnight Service”) for the Carrier 1140 b (inthis case, Airborne) to which that Carrier cell entry corresponds.

As depicted in FIG. 36A, the color for the Carrier identified as“Airborne” 1140 b is depicted in the color coding legend 1062 with aright-diagonal cross-hatch symbol 1140 a. Accordingly, each Carrier cellentry contained within the Graphic Array with the right-diagonalcross-hatch symbol, e.g., 1065, corresponds to a delivery of the SubjectParcel supported by the Carrier “Airborne.” Appearing in each of thecolor-coded Carrier cell entries, e.g., 1065 is a graphic element, e.g.,1065 a, and a monetary value, e.g., 1065 b. The monetary value, e.g.,1065 b corresponds to the price that the corresponding Carrier wouldcharge to deliver the Subject Parcel according to the time 1064-3 anddate 1063-1 specified according to the row and column of which theintersection (which, in the case described is cell 1071-3-1) containsthe Carrier cell entry 1065. For example, as depicted in FIG. 36A, theCarrier cell entry 1065, depicted with the right-diagonal cross-hatchsymbol, contains the monetary amount “$9.00.” Accordingly, the amount$9.00 is the price that the Carrier Airborne would charge to deliver theSubject Parcel at the identified time of 12:00 p.m. 1064-3 on theidentified date of Tuesday, Sep. 28, 1999 1063-1.

Similarly, as depicted in FIG. 36A, the color for the Carrier identifiedas “FedEx” 1141 b is depicted in the color coding legend 1062 with aleft-diagonal cross-hatch symbol 1141 a. Accordingly, each Carrier cellentry contained within the Graphic Array with the left-diagonalcross-hatch symbol, e.g., 1147, corresponds to a delivery of the SubjectParcel supported by the Carrier “FedEx.”

Further, as depicted in FIG. 36A, the color for the Carrier identifiedas “UPS” is depicted in the color coding legend 1062 with a verticalcross-hatch symbol 1142. Accordingly, each Carrier cell entry containedwithin the Graphic Array with the vertical cross-hatch symbol, e.g.,1148, corresponds to a delivery of the Subject Parcel supported by theCarrier “UPS.”

Similarly, as depicted in FIG. 36A, the color for the Carrier identifiedas “USPS” is depicted in the color coding legend 1062 with a horizontalcross-hatch symbol 1143. Accordingly, each Carrier cell entry containedwithin the Graphic Array with the horizontal cross-hatch symbol, e.g.,1149, corresponds to a delivery of the Subject Parcel supported by theCarrier “UPS.”

In the embodiment of the Graphic Array depicted in FIG. 36A, the GraphicArray is dynamically dimensioned. For instance, only the dates and days(1063-1 through 1063-3) for which delivery that conforms to theparticular Shipper's Parcel Specifications for the particular SubjectParcel are displayed across the top of the graphic. For example, for thedate Tuesday, Sep. 28, 1999 (1063-1), at the time 5:00 p.m. (1064-6), noCarrier supports delivery of the Subject Parcel.

Further, as depicted in FIG. 36A, only the times (1064-1 through 1064-6)during which at least one of the Carrier/Services identified assupporting the delivery are displayed along the viewer's left side ofthe Dynamically Dimensioned Multi-Carrier Graphic Array online display.

Still further, as depicted in FIG. 36A, a Carrier cell entry, e.g.,1065, is displayed for each of, but only for each of, theCarriers/Services that support delivery for a particular day and time inthe cell of the Graphic Array that represents delivery on a particularday and at a particular time. When the circumstances require, the Systemdisplays one or more Carrier cell entries in a single cell. Forinstance, cell 1071-3-1 contains two entries, 1065 and 1149; whereascell 1071-1-1 contains only a single cell. Accordingly, as depicted inFIG. 36A, the cell size expands vertically to accommodate multipleCarrier cell entries.

In the exemplary embodiment depicted in FIG. 36A, the color-codinglegend 1062 for each of the Carriers/Services represented in the GraphicArray is displayed with color-coding graphic elements (1140 a through1143 a) and identification labels (1140 b through 1143 b) for eachrelevant Carrier/Service along the viewer's right side of the rating andtiming graphic. Alternatively, instead of the printed name, the logo forthe particular Carrier/Service can be displayed. As another alternative,the Carrier/Service logo can be displayed in color in the color-codinglegend 1062.

The particular arrangement of the color legend 1062 depicted in FIG. 36Aand the particular colors used in the color legend depicted therein areexemplary and are not a limitation of the invention. In an alternativeembodiment, instead of using color, other visually distinctive methodsare used to differentiate between different Carriers/Services. Forinstance, other visually distinctive methods of Carrier/Servicedifferentiation include but are not limited to: three-dimensionaltexture effects, other three-dimensional effects, two-dimensionalmarkings (for instance, dots, cross-hatching, and the like), lightingeffects, graphic symbols (for instance, the logos of theCarriers/Services) and any combination of the aforementioned featureswith color.

In the embodiment of the Graphic Array depicted in FIG. 36A, theexemplary Graphic Array is depicted as horizontally wide enough toaccommodate seven delivery days (1063-1 through 1063-7) within aparticular delivery timespan. The depiction in FIG. 36A of the GraphicArray as a fixed size accommodating up to seven delivery days isexemplary and is not a limitation of the invention. In alternativeembodiments, the Graphic Array online display collapses or expands intotal size to reflect the actual number of rows and columns that need tobe present in order to display the Carrier cell entries for theCarriers/Services that support delivery of the Subject Parcel accordingto the Shipper's Parcel Specifications.

The arrangement as depicted in FIG. 36A of the parcel delivery days anddates (1063-1 through 1063-7) across the top and the parcel deliverytimes (1064-1 through 1064-6) along the left side of the Graphic Arrayis exemplary and is not a limitation of the invention. In onealternative embodiment, the parcel delivery days and dates are displayedacross the bottom, and the parcel delivery times are displayed on theviewer's right side, of the Graphic Array. In other alternativeembodiments, the parcel delivery days are arranged on one of the twosides of the Graphic Array and the parcel delivery times are arrangedalong the top or the bottom of the Graphic Array. In such an alternativeembodiment, the cells of the Graphic Array are expandable horizontallyto accommodate the appropriate number of relevant Carriers/Services.

As depicted in FIG. 36A, the Shipper is asked to input the Expected ShipDate 1060. In the exemplary embodiment depicted, a drop down menuactivation mechanism 1061 provides the Shipper the ability to activate apull down menu (not shown) of seven entries beginning with the currentdate and includes the six days immediately following the current date.The format used is “M/D/YY-Day name”. “Today” and “Tomorrow” aredisplayed appropriately. The number of entries provided by the selectionmechanism, the format of the Expected Ship Date, and other featuresdescribed herein are exemplary and are not a limitation of theinvention.

In the exemplary embodiment depicted in FIG. 36A, once the Shipperselects the Expected Ship Date, the System uses the Expected Ship dateand the other information provided by the Shipper, as in the screensdepicted in FIGS. 15 and 26 described above, to access the CarrierRules, apply the Carrier Rules, and prepare the Graphic Array containingthe delivery prices and delivery times for the Subject Parcel accordingto the Shipper's Parcel Specifications. The System will then generatethe signals necessary to display the Graphic Array and cause the GraphicArray to be displayed on the Shipper's PC.

Once the Graphic Array is displayed, the Shipper can change previouslyinput information and the System will automatically regenerate theGraphic Array with the delivery rates and delivery times that have beenupdated to reflect the new information. For instance, if the Shipperselects a new shipping date, the System will regenerate the GraphicArray with the appropriate new rates and times. The logic forregenerating the Graphic Array is described in more detail below.

In the exemplary embodiment depicted in FIG. 36A, a Ship Location Typedrop down menu activator 1067 is located below the Graphic Array. Theparticular location of the Ship Location Type selection mechanism asdescribed herein is exemplary and is not a limitation of the invention.The list of locations is the same as the Shipping Location Type dropdown menu described above in the description of FIGS. 15 and 26. If theShipping Location class is a “ship center”, a “Find Location” button1068 is displayed next to the drop down menu. In order to open the DropOff Locator in a pop-up window, the Shipper places the Shipper's PCcursor on the “Find Location” button 1068 and clicking the Shipper'suser input device. The Origin Zip Code and Ship Location type valuessupplied by the Shipper are used as parameters for the Drop Off Locatorto locate a list possible Drop Off Location choices. The Shipper canselect a Drop Off Location from the Drop Off Locator menu. The systemdynamically responds to changes by the Shipper to Origin Zip Code andShip Location type to present choices of Drop Off Location choices.

Navigational buttons appear at the bottom of the Rates and Times Screendepicted in FIG. 36A. Clicking the “Back” button 117 will return theShipper to the previously displayed screen, which in the embodimentdepicted is the Location and Package Screen as depicted in FIGS. 15 and26. Clicking the “Next” button 102 will cause the next screen, which inthe embodiment depicted is the Service Option Screen (FIG. 28), to bedisplayed but only if the Shipper has selected a particular Carrier cellentry. For example, if the Shipper click on a particular Carrier cellentry such as 1065, the System will allow the Shipper to then click onthe “Next” button 102 and proceed to the Service Option Screen asdepicted in FIG. 28.

If a user returns to the Rates and Times Screen (FIG. 36A) from theService Option Screen (FIG. 28), any Service Options selected by theShipper from the Service Option Screen (FIG. 28) will effect thedisplayed rates and will be displayed (not shown) as abbreviations belowthe Shipping Location field 1066.

The System in an exemplary eCommerce embodiment such as the onedescribed here creates a multi-carrier, multi-service, shipping costcomparison Graphic Array in much the same way as is disclosed above withregard to the creation of the Graphic Array in an exemplary simplifiedInternet embodiment. The difference is that in an eCommerce embodiment,instead of collecting only Shipper input, the System collectsorigination data including origin zip code, subject parcel data, andCarrier/Service filtering data from the Seller, and then completes theParcel Specifications for the subject parcel by collecting input fromthe Buyer, including destination zip code.

Using the subject parcel's Parcel Specifications, the System isprogrammed to access databases containing information about eachsupported Carrier. Each supported Carrier has a unique rating schedule,delivery and pickup rules and schedules, and certification requirements(the “Carrier Rules”). The System is further programmed to apply eachsupported Carrier's Rules to each Shipper's Parcel Specifications forthe corresponding Subject Parcel. The System calculates the ShippingCharges based on zip-to-zip pricing where the Seller has provided theorigin zip code and the Buyer has provided the destination zip code.

In an eCommerce embodiment, if the Seller selected as the Seller'spreference, “Item cost includes shipping charges” (170, FIG. 21), thenthe rates displayed will be “FREE”. If the Seller selected as theSeller's preference, “Buyer pays actual shipping charges” (171, FIG.21), then the rates displayed with be the total shipping charge ascalculated according to each Carrier's rules for each Service availableaccording to the Seller's expressed preferences. If the Seller selectedas the Seller's preference, “Buyer pays shipping and additional charges”(172, FIG. 21), then the System will calculate and display rates thatare the sum of: 1) the shipping rate for the applicable serviceaccording to each Carrier's rules; 2) If the Seller checked “AddPercentage of Shipping Cost” (173, FIG. 21), the product of thepercentage entered in the Percentage of Shipping Cost field (174, FIG.21) and the total shipping rate calculated according to the Carrier'srules; 2) if the Seller checked “Add Fixed Handling Charge” (175, FIG.21), the dollar value entered in the Fixed Handling Amount field (176,FIG. 21); and 4) if the Seller indicated “Add System Service Fee” (177,FIG. 21), then the System Service Fee amount as indicated in the Systemdatabase 22.

The Dynamically Dimensioned Multi-Carrier, Multi-Service Graphic Arrayonline display presents only rating and delivery timing information forthe Carriers that offer shipping of the particular Subject Parcelaccording to the particular Shipper's Parcel Specifications and whichconform with the Seller's Carrier/Service preferences as selectedaccording to the available options as described above regarding e.g.,FIGS. 19 and 20.

FIG. 36F is a graphic representation of an alternative exemplaryDynamically Dimensioned Multi-Carrier, Multi-Service Graphic Arrayonline display as a Preview Rates Screen (also referred to in someembodiments as a Rates and Times Screen) in an alternative exemplaryembodiment of the invention. The Graphic Array format of the PreviewRates Screen depicted in FIG. 36F is sortable by price (i.e., cheapestfirst), by delivery time (i.e., fastest is first), or preferred carrier,as governed by the enterprise and User preferences. The Preview RatesScreen provides the User with the capability to optimize the Rates 5308according to the Best Price 5136, or the Fastest Delivery 5135.

The exemplary Preview Rates Screen depicted in FIG. 36F depicts an arrayof dates for delivery 5303-5305, multiple Carriers, e.g., 5128 (UPS),5310 (FedEx), and 5311 (Airborne Express). If the Carriers that provideServices to ship the package according to the User's specificationsprovide such services on more days than space exists on a single screendisplay of the Rate Grid, left and right scroll buttons (not shown) areprovided.

The exemplary Preview Rates Screen depicted in FIG. 36F is expandablefor each Carrier to display multiple Services for that Carrier, e.g.,5300 for UPS. The Services for a Carrier can be displayed by the User byclicking a scroll down button, e.g., 5129 for UPS. Each listed Servicefor the Carrier identifies the time for delivery, e.g., 5306. When thePreview Rates Screen is displayed, the Carrier for which the User hasspecified a preference (if such a preference has been specified) isdisplayed in the expanded mode, such as is depicted in FIG. 36F for UPSso that all Services supporting shipment of the subject parcel accordingto the User's specifications are displayed 5300; Carriers for which nopreference has been indicated are displayed in contracted mode, such asis the case for Fed Ex 5310, Airborne Express 5311 and UPS 5128.

In the embodiment depicted in FIG. 36F, only the Carriers and Servicesthat support shipment of the subject parcel according to the User'sspecifications are displayed. In one embodiment of the invention, theUser can limit the default display of Carrier and Service comparison tocertain Carriers and certain Services. In one such embodiment of theinvention, a Show All button (not shown) is provided. Clicking the ShowAll button causes the System to display all Carriers, Services, and Daysof Delivery that support shipment of the subject parcel according to theUser's specifications, even if the User has previously limited theavailable Carriers, Services and Days of Delivery.

A price is displayed in an Array cell, e.g., 5307, 5302, forCarrier/Service that supports delivery of the subject parcel on thespecified day of delivery 5303-5305. According to the User'sOptimization Selection 5135-5136, an Optimizer icon 5301 is displayed inthe particular Graphic Array cell entry that reflects the optimalCarrier/Service.

As was described above, each Carrier is represented in the GraphicArray/Rate Grid by a different color. In the embodiment of the Rate Griddepicted in FIG. 36F, the optimally rated shipping entry for eachCarrier is highlighted in the color for that Carrier; all other entriesfor that Carrier are in grey. The presence or absence of Carriers in theGraphic Array display is driven by User-specified preferences, if any,and by service choices the user has made (for example, by choosing abilling option that only certain Carriers support).

The rates calculated and displayed in the Graphic Array arecustomizable. Some Users may wish to see the iShip System transactioncharge included in the rate quote. In one embodiment of the invention, aRating button is provided on the same screen on which the Graphic Arrayis displayed, with which the User can toggle the rates displayed in theGraphic Array back and forth between the actual shipping rates(including all discounts and fees) and the rate that the Carrier chargesfor shipping.

b) Generation of the Graphic Array Display

To develop the rates for display in a Graphic Rates Comparison Arraysuch as the ones depicted in FIGS. 36A and 36F, the System ratingcomponent is instantiated in the server-side script. The ratingcomponent's rate information method is invoked with the rate parametersembedded in the URL. Based on Carriers' business rules, the rates andtheir service option charges for all Carriers/Services are calculatedfrom each respective Carrier's zone data, service/delivery time data andrate data.

The System keeps the Carrier data up-to-date in the System database 22.The application does not use any carriers' Application Program Interface(API) functions to get the rate information. All of carrier rate data isstored in the System database 22 and all business rules to calculate therates are implemented within the System.

FIGS. 36B through 36E are high level data retrieval and logic flowdiagrams depicting the data and high level logic that the system uses tocalculate a shipping rate. As depicted in FIG. 36B, the followingshipping information is used to calculate a shipping rate: Origin postalcode, Destination postal code, Weight, Packaging, Drop off/Pickup,Country code 3001. For each Carrier 3002, the rating component of theSystem uses the origin and destination postal codes 3003. The ratingcomponent of the System obtains 3003 the zone id from the zone table3008 and gathers 3004 the time for deliveries for all available servicesfrom the service delivery time table 3009. From the rate table 3010, therating component obtains services charges for the zone id, packagingtype and weight 3005. For each service, the rating component gathers allpossible service options charges 3006. After gathering necessaryinformation, the rating component returns an array of rate information3007. Each element in the array represents a Carrier/Service andconsists of service charge, service option charges, and delivery times.

The System calculates the rates according to the following overviewlogic as depicted in FIGS. 36C-36D. As depicted in FIGS. 36C through36D, the System retrieves all rate IDs (published, net, and retail) byjoining the following database tables on the System's AccountNo:AccountAndCarrierAcnt; CarrierAccount; RateDefinition 3020.

As depicted in FIGS. 36C through 36D, the System then determines thebilling rules for all of the Carrier/Service combinations and theirservice options by joining the following tables on CarrierID, ServiceID,and ServiceOptionID: BillingOption; BillingOptionAndService;BillingoptionAndServiceOption 3021.

-   -   As depicted in FIGS. 36C through 36D, for each carrier 3022, the        System performs the following procedures: 1) determine if the        particular carrier supports the given billing option based on        step 2) (through 3026). If not, continue with the next carrier        3027; 2) Apply carrier business rules, including: a) Calculate        dimensional weight 3023; b) Determine billable weight 3024:        actual weight, dimensional weight, oversize weight or letter        weight; c) Validate package weight and dimensions 3025; (If the        rate input violates carrier business rules 3026, continue to        next carrier 3027); 3) If the answer to test process 3026 is        “no” (package weight and dimensions do not violate carrier        business rules), then determine the zone ID from CarrierZone        table for the given origin/destination postal codes 3028; 4)        Determine service delivery times 3029 (including Saturday/Sunday        delivery times) by joining the following tables on destination        postal code: a) CarrierDeliveryArea; b)        CarrierServiceDelTime; 5) Determine all service charges from        CarrierRate table by RateID, ZoneID, ServiceID and Weight        3030; 6) Determine the service option charges for each        Carrier/Service 3031 by joining the following tables on        CarrierID and ServiceID: ServiceOption; ServiceOptionAttribute        ServiceAndServiceOption; and 7) Apply billing options to service        option charges 3032 (different service option charges could be        billed to different parties for various billing options).

As depicted in FIG. 36E, the expected delivery times for eachCarrier/Service returned in the rate information determine the placementof the rate grid for the particular Carrier/Service cell: the deliverydate determines the columns 3040 while the delivery time resolves therows 3041. In the event that multiple rate entries collide (yes to test3042), the alphabetical order of the particular Carrier's name isfurther used to determine the Graphic Array entry order within the samedate and time bucket 3043. If there is no collision or once a collisionis resolved 3043, the same Carrier/Service can be placed in a secondtime slot in the grid under Saturday or Sunday column 3045 if theSaturday or Sunday delivery is applicable to the particularCarrier/Service 3044. If Saturday or Sunday delivery does not apply (noto test 3044), or once a Saturday/Sunday time slot is indicated 3045,the System returns 3046.

In an eCommerce embodiment of the invention, a Shipper/Seller canpreview a shipping rate comparison Graphic Array prior to copying theSystem-created Link, e.g., 203 a as depicted in FIG. 25, for theSeller's eCommerce site. To preview the Graphic Array comparison ofshipping costs, the Seller clicks on the Preview button 198, such as isdepicted in FIG. 25. FIGS. 37A and 37B represent a System interactivitydata and logic flow diagram depicting an exemplary embodiment of theCreate Link and the Buyer's Preview Shipping Rates functionality in aneCommerce embodiment of the present invention. FIGS. 37A and 37B depictthe interactivity between the Seller's 8-1 and Buyer's 8-2 clientcomputers and the System's server computers 20 a-21 z regarding thisfunctionality. Also depicted are the data accesses to the Systemdatabase 22. An arrow 230 extending from the top of the diagram andpointing down towards the bottom of the figure graphically representsthe passage of time.

As depicted in FIGS. 37A and 37B, the Seller, using the Seller'scomputer 8-1, clicks on the Create a Seller's Link selection option 331notifying the System servers, e.g., 21 a-21 z, to generate a display ofthe Create a Seller's Link screen 332 for display on the display monitorof the Seller's computer 8-1. In one embodiment, the Servers 21 a-21 zsend 332 the necessary information and instructions to build thehyperlink to the Seller's computer 8-1. The Seller enters the link textand clicks the go button and the Seller's computer 8-1 creates the Link333. The Seller then copies the link, returns to the Seller's web page,and pastes the link 334 in the description of the item to be sold at theeCommerce/eAuction Provider's web site 345.

The Buyer, using the Buyer's computer 8-2, enters the Seller's web page335 at the eCommerce/eAuction Provider's web site 345. The Seller's webpage at the eCommerce/eAuction Provider's web site 345 displays the itemdescription with the hyperlink to the System 336 to the Buyer's computer8-2. The Buyer clicks on the hyperlink 337, causing the System's servers20 a-20 z to access 338 the System database 22 to retrieve 339 theSeller's account and eCommerce shipping preference information. TheSystem servers 21 a-21 z send a screen to the Buyer's computer 8-2requesting delivery destination information 340. The Buyer at theBuyer's computer 8-2 enters the delivery destination information andclicks on the Get Rates button 341 which signals the System Servers 20a-21 z to prepare the multi-carrier, multi-service Graphic Array. TheSystem Servers 20 a-20 n access 342 the System data base 22 and retrieve343 the Seller's preferences and account information. The System Servers21 a-21 z calculate the rates and prepare the Graphic Array 344 fordisplay on the display monitor of the Buyer's computer 8-2.

Whether or not the Buyer/Bidder (sometimes simply referred to herein asthe Buyer) uses the hyperlink 303 to preview the shipping charges, ifthe Buyer buys (or is the high bidder), the Seller is provided with theBuyer's (or high bidder's) email address and name 54 (as depicted inFIG. 10C) either directly or by the sponsoring Provider. At that point,the Seller enters the System to supply the System with Buyer information(57 and 58 as depicted on FIG. 10D) so that the System can contact theBuyer (80, FIG. 10D) for details and to facilitate the purchase andshipping of the item.

In contrast to the collection of both Seller and Buyer information in aneCommerce embodiment, the generation of the Graphic Array in theexemplary simplified Internet embodiment is accomplished using inputfrom the Shipper only. FIG. 38 is a simplified flow diagram depicting anexemplary high level overview logic flow of the System and theinteraction with the Shipper/User such as in an exemplary simplifiedInternet embodiment of the invention. As depicted in FIG. 38, at leastone of the Servers 20 a-21 z are programmed to provide a User Interface(“UI”) that prompts each Shipper user for information about a particularparcel (the “Subject Parcel”) and the Shipper's shipping and deliveryrequirements (“Shipper Parcel Specifications”) 1401 a-1401 n. At leastone of the Servers 20 a-21 z is programmed to receive as a set of inputdata a particular Shipper's Shipper Parcel Specifications for aparticular Subject Parcel 1402. In response to each Shipper's ShipperParcel Specifications, at least one of the Servers 20 a-21 z accesses1403 one or more databases of information concerning, among otherthings, the Carrier Rules for each of the Carriers supported by theSystem (the “Supported Carriers”) 1404 a through 1404 n. The CarrierRules for each of the Supported Carriers are contained in one or moredatabases 1404 a through 1404 n.

As further depicted in FIG. 38, the System then applies the CarrierRules for all Supported Carriers to each particular set of ShipperParcel Specifications 1403. From the result of the application by theSystem of the Carrier Rules to a particular set of Shipper ParcelSpecifications, the System prepares a Graphic Array that displays arating and timing comparison of the delivery services by the supportingCarriers that are available to provide the delivery of the SubjectParcel according to the Shipper's Parcel Specifications 1405. The Systemthen formats the Graphic Array for display on the Shipper's PC 1406, andgenerates the signals to the Shipper's PC to display the formattedGraphic Array 1407.

In one embodiment of the invention, the System provides multiple modesof operation, among which are the Service Comparison Mode and theShipping Mode. The Service Comparison Mode requires origin anddestination zip codes but does not require full address information. Thepurpose of the Service Comparison Mode is to provide the Shipper withmulti-Carrier comparisons of rates, and shipping and delivery optionsand requirements for each of multiple Carriers. In the Shipping Mode,the Shipper must provide the full address and contact information. Thepurpose of the Shipping Mode is to print a shipping label or otherwiseprovide the information necessary to prepare a shipping manifestdocument. Shipper Parcel Specifications are input in both the ServiceComparison Mode and the Shipping Mode.

FIGS. 39A through 39C are simplified flow diagrams depicting the initialTiming and Rating procedure to generate a Graphic Array in an exemplarysimplified Internet embodiment of the invention. In the embodiment ofthe invention depicted in FIGS. 39A through 39C, the functions of theShipper entering shipping information 1150, displaying errors to theShipper that insufficient shipping information has been provided andprompting the Shipper for additional information 1153, and displayingthe Carrier/Service rate and time graphic 1160, are all processed by theWeb Browser at the Client. In the embodiment depicted, all otherfunctions and processes depicted in FIGS. 39A through 39C are performedby one or more of the NOC Servers.

It should be noted that the depicted separation of functions between theWeb Browser at the Client on the one hand and the NOC Servers on theother hand represents an initial procedure to construct the GraphicArray in response to initial Shipper input of Shipper ParcelSpecifications. As is explained in more detail below, after the initialconstruction of the Graphic Array, the System can distribute certain ofthe functions for supplemental regeneration of the Graphic Array to theWeb Browser Client.

As depicted in FIGS. 39A through 39C, the Shipper (User) enters shippinginformation (Shipper Parcel Specifications) 1150. The System validatesthe shipping information 1151.

In the embodiment depicted, at a minimum, the System requires SourcePostal Code, Destination Postal Code, Parcel Weight, Type of Shipment,and the Shipping Location in order to determine a timing schedule andrates for each supported Carrier. If at 1152 the Shipper has notprovided at least these minimum specifications, then the System displayserror messages 1153 prompting the Shipper to input further ShipperParcel Specifications 1150.

Continuing with FIGS. 39A through 39C, if the Shipper has supplied theminimum required specifications, then the System accesses the ShipperDatabase 1195 to identify any user-specified Carrier designations and todetermine the Carrier accounts for the appropriate Shipper 1154. Usingthe Shipper Parcel Specifications, the System then accesses the CarrierDatabases (1404 a through 1404 n) and determines all possibleCarrier/Services that support shipping of the subject parcel 1155.

It should be noted that in some embodiments, the Shipper can restrictthe identity of Carriers to be used in the construction of the GraphicArray. A Shipper may choose to restrict the System to certain Carriers,for instance, if the Shipper prefers to work only with certain Carriers.

Continuing with FIGS. 39A through 39C, the System then examines eachCarrier/Service in the set of supporting Carrier/Services 1156. The nextstep 1157 is a juncture for return of control from a number of points inthe System logic and is performed for each Carrier/Service in the set ofsupporting Carrier/Services.

If the System has examined all possible supporting Carrier/Services1158, the System assembles the Graphic Array from the delivery rate set1159 and displays the Graphic Array to the user 1160. As was previouslyexplained, the dimensions of the Graphic Array are dynamic.

As long as there are further Carrier/Services that remain to be examinedin the set of supporting Carrier Services, the System continues toperform the process described below.

Using the Expected Shipping Date, the System switches theCarrier/Service's shipping timespan into possible delivery dates andtimes 1161. Next 1162, the System determines whether the shippingtimespan ends on a Saturday 1163. If so, the System accesses the CarrierDatabase (1404 a through 1404 n) to determine whether the particularCarrier/Service supports Saturday Delivery 1164. If the particularCarrier/Service does not support Saturday Delivery, then the particularCarrier/Service is eliminated 1177 from the delivery rate set and theSystem proceeds with the next Carrier/Service in the delivery rate set1157.

If the particular Carrier/Service supports Saturday Delivery, the Systemdetermines the appropriate Saturday delivery rate for the particularCarrier/Service 1165.

Continuing with FIGS. 39A through 39C, next (continuing after process1165, or if the answer to test process 1163 is “no” (shipping timespandoes not end on a Saturday)), the System determines whether the shippingtimespan ends on a Sunday 1168. If the shipping timespan ends on aSunday, the System accesses the Carrier Database (1404 a through 1404 n)to determine whether the particular Carrier/Service supports Sundaydelivery 1166. If the particular Carrier/Service does not support Sundaydelivery, then the particular Carrier/Service is eliminated from thedelivery rate set 1177 and the System proceeds with the nextCarrier/Service in the delivery rate set 1157.

If the particular Carrier/Service supports Sunday Delivery, the Systemdetermines the appropriate Sunday delivery rate for the particularCarrier/Service 1167.

The System then (continuing after process 1167, or if the answer to testprocess 1168 is “no” (shipping timespan does not end on a Sunday))determines whether there is a business day delivery within the shippingtimespan 1169. If so, the System accesses the Carrier Database (1404 athrough 1404 n) to determine whether the particular Carrier/Servicesupports business day delivery 1170. If the particular Carrier/Servicedoes not support business day delivery, then the particularCarrier/Service is eliminated from the delivery rate set 1177 and theSystem proceeds with the next Carrier/Service in the delivery rate set1157.

If the particular Carrier/Service supports business day delivery, theSystem determines the appropriate business day delivery rate for theparticular Carrier/Service 1171.

Continuing with FIGS. 39A through 39C, the System next (continuing afterprocess 1171, or if the answer to test process 1169 is “no” (there is noassociated business day delivery)) determines whether the Shipper hasrequested E-Mail delivery notification 1172. If so, the System accessesthe Carrier Database (1404 a through 1404 n) to determine whether theparticular Carrier/Service supports E-Mail delivery notification 1173.If the particular Carrier/Service does not support E-Mail deliverynotification, then the particular Carrier/Service is eliminated from thedelivery rate set 1177 and the System proceeds with the nextCarrier/Service in the delivery rate set 1157.

If the particular Carrier/Service supports E-Mail delivery notification,the System adds the appropriate charge for the E-Mail deliverynotification service to each of the particular Carrier/Service'sdelivery rates 1174.

Continuing with FIGS. 39A through 39C, the System then (continuing afterprocess 1174, or if the answer to test process 1172 is “no” (e-maildelivery notification not selected)) determines whether the Shipper hasrequested verbal delivery notification 1175. If so, the System accessesthe Carrier Database (1404 a through 1404 n) to determine whether theparticular Carrier/Service supports verbal delivery notification 1176.If the particular Carrier/Service does not support verbal deliverynotification, then the particular Carrier/Service is eliminated from thedelivery rate set 1177 and the System proceeds with the nextCarrier/Service in the delivery rate set 1157.

If the particular Carrier/Service supports verbal delivery notification,the System adds the appropriate charge for the verbal deliverynotification service to each of the particular Carrier/Service'sdelivery rates 1178.

Next 1179 (continuing after process 1178, or if the answer to testprocess 1175 is “no” (verbal delivery notification no selected)), theSystem determines whether the Shipper has requested that theCarrier/Service guarantee delivery time 1180. If so, the System accessesthe Carrier Database (1404 a through 1404 n) to determine whether theparticular Carrier/Service supports guaranteed delivery times 1181. Ifthe particular Carrier/Service does not support guaranteed deliverytimes, then the particular Carrier/Service is eliminated from thedelivery rate set 1177 and the System proceeds with the nextCarrier/Service in the delivery rate set 1157.

If the particular Carrier/Service supports guaranteed delivery times,the System adds the appropriate charge for the guaranteed delivery timesservice to each of the particular Carrier/Service's delivery rates 1182.

Continuing with FIGS. 39A through 39C, the System then (continuing afterprocess 1182, or if the answer to test process 1180 is “no” (guaranteeddelivery time not selected)) determines whether the Shipper hasrequested a “Call for Pickup” shipping location 1184. If so, the Systemaccesses the Carrier Database (1404 a through 1404 n) to determinewhether the particular Carrier/Service supports “Call for Pickup”services 1185. If the particular Carrier/Service does not support “Callfor Pickup” services, then the particular Carrier/Service is eliminatedfrom the delivery rate set 1177 and the System proceeds with the nextCarrier/Service in the delivery rate set 1157.

If the particular Carrier/Service supports “Call for Pickup” services,the System adds the appropriate charge for the “Call for Pickup” serviceto each of the particular Carrier/Service's delivery rates 1186.

Continuing with FIGS. 39A through 39C, the System next (continuing afterprocess 1186, or if the answer to test process 1184 is “no” (selectedshipping location is not “Call for Pickup”)) determines whether theShipper has requested a “Residential Delivery” 1187. If so, the Systemaccesses the Carrier Database (1404 a through 1404 n) to determinewhether the particular Carrier/Service supports “Residential Delivery”services 1188. If the particular Carrier/Service does not support“Residential Delivery” services, then the particular Carrier/Service iseliminated from the delivery rate set 1177 and the System proceeds withthe next Carrier/Service in the delivery rate set 1157.

If the particular Carrier/Service supports “Residential Delivery”services, the System adds the appropriate charge for the “ResidentialDelivery” service to each of the particular Carrier/Service's deliveryrates 1189.

The System then (continuing after process 1189, or if the answer to teststep 1187 is “no” (residential delivery no selected)) determines whetherthe Shipper has requested a “Loss Protection” services 1190. If theanswer to test process 1190 is “no” (Loss Protection not selected) thenthe System proceeds with the next Carrier/Service in the delivery rateset 1157. If Loss Protection is selected, the System accesses theCarrier Database (1404 a through 1404 n) to determine whether theparticular Carrier/Service supports “Loss Protection” services 1191. Ifthe particular Carrier/Service does not support “Loss Protection”services, then the particular Carrier/Service is eliminated from thedelivery rate set 1177 and the System proceeds with the nextCarrier/Service in the delivery rate set 1157. The System thendetermines 1192 whether the requested loss protection is within theservice's range; if not, the System proceeds with the nextCarrier/Service in the delivery rate set 1157.

Continuing with FIGS. 39A through 39C, if the particular Carrier/Servicesupports “Loss Protection” services, and if the requested lossprotection is within the service's range the System calculates theappropriate charge for the “Loss Protection” service and adds theappropriate charge to each of the particular Carrier/Service's deliveryrates 1193 before proceeding with the next Carrier/Service in thedelivery rate set 1157.

FIG. 40 is a graphic representation depicting an exemplary embodiment ofa multi-carrier, multi-service shipping rates comparison Graphic Array320 in an exemplary eCommerce embodiment of the invention.

c) Automatic Dynamic Regeneration of Display

In the exemplary embodiments of the invention described here, the Systemautomatically and dynamically regenerates the display of the GraphicArray and certain portions of other screens when the Shipper makesonline changes to Shipper input. To do this, the System generatesexecutable code which it distributes with certain displayable frames tothe Web Browser Client. This distribution of code for purposes ofregenerating the Graphic Array differs from the initial generation ofthe Graphic Array as was described above. For example, in the embodimentof the invention depicted in FIGS. 39A through 39C, in the initialdevelopment of the Graphic Array, the System distributes the functionsthat initially generate the Graphic Array as follows: the Shipperentering shipping information 1150, displaying errors to the Shipperthat insufficient shipping information has been provided and promptingthe Shipper for additional information 1153, and displaying the GraphicArray 1160, are all processed by the Web Browser at the Client; allother functions and processes depicted in FIGS. 39A through 39C areperformed by one or more of the NOC Servers 20 a-21 z.

Distribution to the Web Browser Client by the System of executable codethat regenerates the Graphic Array provides the capability todynamically reflect in the Graphic Array any changes that the Shippermay enter to the various Shipper Parcel Specifications; the GraphicArray immediately displays the new information without requiring theShipper to request a recalculation, such as by clicking on a“Regenerate” button or the like.

To facilitate regeneration of the Graphic Array, the System generatesexecutable code which it distributes with the frame, such as the framethat is displayed to the user for collecting the Parcel Specifications,to the Web Browser Client. A displayable frame is a set of informationfor display on the client display device. For example, in FIG. 36A, inone embodiment of the invention, a first frame of the screen depicted inFIG. 36A comprises the Title “Rates & Times” 1109 a, the instruction“Click on the price to select a delivery date, time and carrier.” 1109b, the legend “Date you expect to ship your package:” 1109 c, the inputfield for the Expected Shipping Date 1060, the legend “I'll ship thepackage from:” 1109 d and the input field for the Shipping Location1066; a second frame of the screen depicted in FIG. 36A comprises theGraphic Array.

As the System generates the display of each frame, the System generatesexecutable code which it distributes with, e.g., the Rate & Times frame,to the Web Browser Client. Thereafter, the Web Browser Client uses theexecutable code to automatically regenerate the display of the GraphicArray each time the Shipper makes changes to the Shipper ParcelSpecifications. In one embodiment of the dynamic regeneration aspect ofthe invention, the executable code distributed to the Web Browser Clientuses JavaScript.

In some cases, the executable code sent to the Web Browser Clientprovides the information and the capability to regenerate the GraphicArray without any further communication with the Server. In other cases,the Web Client Browser must return control to the Server so that theServer can access data maintained by or accessible by the Server; theServer then regenerates the Graphic Array or otherwise provides the WebBrowser Client with the information necessary to regenerate the GraphicArray.

In an exemplary embodiment of the automatic dynamic regeneration aspectof the invention, the executable code distributed to the Web BrowserClient contains the logic to apply Carrier Rules to Shipper ParcelSpecification changes. For instance, Shipper changes to the ServiceOptions screen as depicted in FIG. 28 would be automatically processedby the Web Client Browser and the Web Client Browser would regeneratethe Single Day Rate Graphic Array depicted therein to reflect theShipper changes. In one such automatic dynamic regeneration embodiment,only those functions that do not require further access to the relevantCarrier's database are distributed to the Web Browser Client.

It should be noted that, according to the automatic dynamic regenerationaspect of the invention, if after the Shipper views the Graphic Arraythe Shipper enters changes to any of the factors with which the Systemcalculates the rates and develops the Graphic Array, the System uses asimilar logic flow to regenerate the Graphic Array as was explainedabove in relation to FIGS. 39A through 39C.

The dynamic regeneration capability is used to automatically regenerateresponse screens in many places throughout the System. For instance, aswas mentioned above, as in the case of FIG. 36A, if the Shipper changesOrigin Zip Code and/or Ship Location Type, the System will automaticallyregenerate a list of possible Drop Off Location choices.

d) Completing Parcel Specifications and the Buyer's Information

In an eCommerce embodiment of the invention, the System collectsinformation from both a Seller (the Shipper) and a Buyer (theRecipient). The Seller (Shipper) inputs information about the parcel tobe shipped and initial information about the Buyer. The Buyer theninputs information such as shipping address and payment information.Depending upon the Seller's preferences, the Buyer may also be asked tochoose one of multiple carriers and multiple shipping services.

FIG. 41 is a graphic representation of a Seller's Buyer InformationScreen (57, FIG. 10D) in an eCommerce embodiment of the invention. TheSeller enters the screen in one embodiment by logging in to the Systemand then selecting the Sell It option 31 a and by selecting the RequestBuyer Info submenu option 31 b-3. The System provides the Seller withinstructions to complete the requested data 350. The Seller inputs theBuyer's Name 351, the Buyer's e-mail address 352, an Order/Item number353, a Description of the Goods to be Shipped 354 a (the Seller mayscroll through the description using the scroll buttons 354 b and 354 cif the description exceeds the online screen window for the descriptiontext), and a message to the buyer 355 a (the Seller may scroll throughthe message using the scroll buttons 355 b and 355 c if the messageexceeds the online screen window for the message text).

Buyer information and package/item information is mapped by the Systeminto the appropriate shipping data fields (i.e., Buyer name is mapped toRecipient Company/name; Buyer e-mail is mapped to Recipient e-mail,item/order number is mapped to reference number, etc.).

Clicking on the Next button 102 will cause the System to display theNext screen, which in this case is the package specific informationscreen (58, FIG. 10D) as depicted in FIG. 42.

FIG. 42 is a graphic representation of an exemplary embodiment of aSubject Parcel data screen. The Seller inputs the weight by clicking onthe weight pull down menu button 358-2 and selecting a weight 358-1 fromthe list. An “Irregular or Non-Standard Packaging” indicator 359 isprovided. The Seller selects Loss Protection, the default being BasicCoverage 360, or Declared Value 361. If the Seller selects DeclaredValue 361, the Seller must enter a value 362 greater than $0.00 and lessthan or equal to $50,000.00. The Seller also enters the Item Cost to bedisplayed to the Buyer 364 and indicates whether or not the Systemshould show the Buyer the total of the Item Cost and Shipping Charges363. Once the Seller has entered the information, if the Seller clickson the Send button 365, the System validates the information input andprepares an e-mail to the Buyer (59, FIG. 10D).

At this point, the System generates a System package tracking number. ASystem tracking number is a unique number generated internally by theSystem to identify a particular package shipped using the System. Oneembodiment of the way in which the System generates a System packagetracking number is disclosed below in the Tracking section of thedisclosure of the present invention.

FIG. 43 is a graphic representation of an exemplary embodiment of aSystem-prepared e-mail to the Buyer. The System builds the e-mail tocontain the identification of the System as the sender 370, the e-mailof the Buyer 352 as supplied by the Seller, a Subject identificationcontaining the item number 353 as supplied by the Seller, the Buyer name351 as supplied by the Seller, the Seller name 375 as retrieved from theSeller's account information retrieved after the Seller logged into theSystem before entering Request Buyer Info 31 b-3 (e.g., as depicted inFIG. 24), a Reference number as provided by the Seller 353, instructionsto the Buyer 371 to click on the embedded hyperlink 372, and somefurther instructions to the Buyer 374. The System builds the hyperlink372 according to a preset URL location 372-1 as provided from the Systemdatabase 22, and specifying the System package tracking number 372-3 asthe value for a variable named “T=” 372-2.

If the Buyer's e-mail program is integrated with the Buyer's webbrowser, then the Buyer can click on the hyperlink/URL 372 contained inthe e-mail. Otherwise, the Buyer must copy the hyperlink/URL 372 intothe Address/Location field of the web browser. When the Buyer clicks onthe hyperlink/URL 372, the System displays the first screen (60, FIG.10D) in the Buyer Response process.

FIG. 44 is a graphic representation of an exemplary embodiment of theBuyer Response Introduction screen. The System provides the Buyer withinstructions 380. The System instructs the Buyer 382 to indicate 383 theBuyer's choice not to supply the requested shipping information and anexplanation as to why 384-1. The Buyer can scroll through theexplanation using the up and down scroll keys 384-2 and 384-3 if thetext of the description exceeds the online screen window for the text.The Buyer sends the refusal notification and message by clicking theSend button 385. Otherwise, if the Buyer wishes to proceed, the Buyerclicks the Next button 381 which will cause the System to display aBuyer Shipping Information Collection screen (61, FIG. 10D).

FIG. 45 is a graphic representation of an exemplary embodiment of theBuyer Shipping Information Collection screen (61, FIG. 10D). The Systemrequests that the Buyer input the Buyer's delivery address informationand then click the Next button 389. The Buyer inputs the deliveryaddress information including the Company/Name 390, the Attention toname 391, the street address 392, the floor/room number 393, thedepartment 394, the city 395, the state 396-1 using the pull down menubutton 396-2, the zip code 397, the telephone number 398, the fax number399, and whether the delivery address is a business 400 or a residence401. If the Buyer then clicks the Next button 102, the System validatesthe information supplied by the Buyer and displays a screen (62, FIG.10D) as depicted in FIG. 46 containing a selection as to whether yes 405or no 406 the Buyer wants a guaranteed delivery time. Once the Buyerselects the guarantee choice, then the Buyer clicks the Get Rates button407 to request that the System prepare and display the multi-carrier,multi-service shipping rates comparison Graphic Array 320.

An exemplary embodiment of the Graphic Array 320 in an exemplaryeCommerce embodiment of the invention is depicted in FIG. 46. TheGraphic Array 320 presents a multi-carrier, multi service rate and timeshipping cost comparison as similarly disclosed above and described withrespect to FIG. 36A.

The System creates the Graphic Array in much the same way as isdisclosed above with respect to FIG. 36A except that, with respect tothe eCommerce embodiment, instead of only Shipper input, the Systemcollects origination data including origin zip code, subject parceldata, and Carrier/Service filtering data from the Seller, and thencompletes the Parcel Specifications for the subject parcel by collectinginput from the Buyer, including destination zip code.

Using the subject parcel's Parcel Specifications, the System 1 isprogrammed to access databases containing information about eachsupported Carrier. Each supported Carrier has a unique rating schedule,delivery and pickup rules and schedules, and certification requirements(the “Carrier Rules”). The System 1 is further programmed to apply eachsupported Carrier's Rules to each Shipper's Parcel Specifications forthe corresponding Subject Parcel. The System calculates the ShippingCharges based on zip-to-zip pricing where the Seller has provided theorigin zip code and the Buyer has provided the destination zip code.

The System provides an online display of a Dynamically DimensionedMulti-Carrier Graphic Array such as is depicted in FIG. 46. If theSeller selected as the Seller's preference, “Item cost includes shippingcharges” (170, FIG. 21), then the rates displayed will be “FREE”. If theSeller selected as the Seller's preference, “Buyer pays actual shippingcharges” (171, FIG. 21), then the rates displayed with be the totalshipping charge as calculated according to each Carrier's rules for eachService available according to the Seller's expressed preferences. Ifthe Seller selected as the Seller's preference, “Buyer pays shipping andadditional charges” (172, FIG. 21), then the System will calculate anddisplay rates that are the sum of: 1) the shipping rate for theapplicable service according to each Carrier's rules; 2) If the Sellerchecked “Add Percentage of Shipping Cost” (173, FIG. 21), the product ofthe percentage entered in the Percentage of Shipping Cost field (174,FIG. 21) and the total shipping rate calculated according to theCarrier's rules; 2) if the Seller checked “Add Fixed Handling Charge”(175, FIG. 21), the dollar value entered in the Fixed Handling Amountfield (176, FIG. 21); and 4) if the Seller indicated “Add System ServiceFee” (177, FIG. 21), then the System Service Fee amount as indicated inthe System database 22.

The Dynamically Dimensioned Multi-Carrier, Multi-Service Graphic Arrayonline display presents only rating and delivery timing information forthe Carriers that offer shipping of the particular Subject Parcelaccording to the particular Shipper's Parcel Specifications and whichconform with the Seller's Carrier/Service preferences as selectedaccording to the available options as described above regarding FIGS. 19and 20.

The Buyer uses a user input device such as a mouse, track ball, or thelike, to pick a Carrier and Service. To make the selection, the Buyer,for instance, places the cursor of the Buyer's PC on the displayedCarrier cell entry (e.g., 408 as depicted in FIG. 46; e.g., 1065 asdepicted in FIG. 36A) in the Graphic Array and clicks the Buyer's userinput device (the “Selected Carrier”).

Once the Shipper selects a particular Graphic Array Carrier cellelement, (e.g., 408 as depicted in FIG. 46; e.g., 1065 as depicted inFIG. 36A) the System then processes the shipping transaction. In anexemplary simplified Internet embodiment of the invention, the Systemprocesses the Shipper's shipping transaction using Shipper informationfrom the Shipper Database 1195 (e.g., as depicted in FIG. 39A) andinformation for the Selected Carrier from the Carrier Database 1404 athrough 1404 n (e.g., as depicted in FIG. 39A). In an exemplaryeCommerce embodiment of the invention, the System processes the shippingtransaction using information supplied by both the Seller/Shipper andthe Buyer/Recipient and information for the Selected Carrier.

In an eCommerce embodiment of the invention, once the Buyer selects aCarrier and Service, the System prepares a Shipping Summary Screen (63,FIG. 10D) an exemplary embodiment of which is depicted in FIG. 47. TheSystem reports a summary of the Shipping information including thedelivery address 410, the Carrier/Service 411 and the itemized and totalcharges for the item and shipping 412. In addition, if the Sellerrequested the System to collect payment information, the System providesa drop down selection menu button 413-2 which when clicked will displaya list of the methods of payment 413-1 previously selected by the Seller(e.g., 179 a-179 g, and 180, as depicted in FIG. 21). If a credit cardpayment method is indicated, the Buyer is required to supply a creditcard number 414, and the expiration date month 415-1 (using a drop downmenu button 415-2) and year 416-1 (using a drop down menu button 416-2).The Buyer is instructed to click the Cardholder Information button 417if the cardholder name and address are different than the shipping nameand address 419. If the Cardholder and shipping information match, theBuyer clicks the Send button 418 to send the payment information toprocessing.

In an exemplary simplified Internet embodiment of the invention, theSystem generates a Shipping Summary Screen once the Shipper has picked aparticular Carrier/Service entry from a Graphic Array comparison. FIG.48 depicts an alternative exemplary embodiment of a Shipping SummaryScreen such as in an exemplary simplified Internet embodiment of theinvention. In the embodiment depicted in FIG. 48, the Shipper has pickeda particular Carrier/Service entry from a Graphic Array comparison(e.g., 1065 as depicted in FIG. 36A). The Shipping Summary Screendepicted in FIG. 48 displays the Shipper Parcel Specifications 1110 andprovides a detailed list and total, of the selected Carrier's charges1111. Clicking on the “Next” button 102 causes the display of the firstof a series of several screens (not shown) requesting the necessaryShipper and Recipient information. Once the Shipper has input all of thenecessary information, the Shipper is presented with a final Summary andPayment Screen (not shown), which in addition to the fields depicted inFIG. 48, further requests Payment information, such as Payment Method,Credit Card No., Expiration Date, and Credit Card Type.

Returning to the eCommerce embodiment depicted in FIG. 47, if the Buyerclicks the Cardholder Information button 417, the System displays aCardholder Information collection screen (64, FIG. 10D), an exemplaryembodiment of which is depicted in FIG. 49. The Buyer is asked to supplythe Cardholder name 420, Street address 421, State 422-1 (using a pulldown menu button 422-2), and zip code 423. The Buyer clicks the Savebutton 424 to save the cardholder information.

As depicted in FIG. 10D, once the Buyer in an eCommerce embodiment hascompleted all Buyer Response screens, the System enters the Systempackage tracking number in the System's Shipping Log for the Seller, anexemplary embodiment of which is depicted in FIG. 50. The System alsonotifies the Seller via e-mail (66, FIG. 10D) that the Buyer hascompleted all of the necessary shipping and payment information.

E. SHIPPING THE PACKAGE

In an exemplary eCommmerce embodiment of the invention, the Systemnotifies the Seller via e-mail (66, FIG. 10D) once the Buyer hascompleted all of the necessary shipping and payment information. Anexemplary embodiment of a Seller notification e-mail is depicted in FIG.51. In the Seller notification e-mail, the System identifies the Systemas the sender 370, the Seller's e-mail 107 (e.g., as depicted in FIG.12) as the recipient 375, and the item number 353. The e-mail contains amessage 425 and instructions 427 to log on to the System 426 to view aShipping Log. The Shipping Log provides a platform with which theShipper/Seller controls the shipping and attendant functions for allpackages shipped or to be shipped by the particular Shipper/Seller.

The Seller can view the Shipping Log by selecting the View Shipping Logsubmenu option 32 b-2 from the Ship It menu option 32 b (which providesvarious submenu options including Shipping Preferences 32 b-1, ViewShipping Log 32 b-2, Ship a Package 32 b-3, Price a Package 32 b-4, SendShipment Notification 32 b-5, UPS End of Day 32 b-6 and Log Off 32 b-7).The Shipper/Seller can control the display order of the Shipping Log byselecting from a choice of several reporting controls. The ShippingLog(65, FIG. 10D) as depicted in FIG. 50 provides reporting controlssuch as Display selection 430 (with a pull down menu button 431), timeperiod 432 (with a pull down menu button 433), and sort by 434 (with apull down menu button 435). The Seller can click on the Update Viewbutton 436 to request an up-to-date report. Each Shipping log line itemcontains the System tracking number 438, the addressee name 437, theCarrier 440 and Service 439, the Ship date 441 and delivery date 442,and control buttons that allow the Seller to request details 443,instruct the system to ship the item 444, void the shipment 445, orreprint a label 446.

FIG. 52 is a graphic representation of an exemplary embodiment of a VoidPackage screen that the System displays if the Seller clicks on the Voidbutton 445 on the Shipping Log. The Void Package screen provides asummary report of the information about the particular package 452,provides a View Details button 451 if the Seller wants additionaldetailed information about the package, and a Void Package button 453 ifthe Seller finally decides to void the identified package.

FIG. 53 is a graphic representation of an exemplary embodiment of aReprint Label screen which provides a report about the package 454, aView Details button 451, and a Generate Label button 455. If the Userclicks the Generate Label button 455, the System will generate and printa shipping label (69, FIG. 10E) for according to the appropriate Carrierand Service, as limited by the Seller and as finally selected by theBuyer.

As mentioned above, in some embodiments, the Shipper can use the Systemto locally print on the Shipper's printer device a bar-coded shippinglabel according the Selected Carrier's certification standards. In someembodiments, the bar-coded shipping label, including two dimensional barcode labels, and other types of shipping labels, can be printed oneither a thermal label printer or on a laser printer. The Shipperspecifies the type of printer to the system during initial setupprocedures. Thereafter, the System uses, as appropriate, the thermalprinter or laser printer module to prepare the label image for printingon the Shipper's printer.

FIG. 54 depicts a flow diagram of one embodiment of the aspect of theinvention that provides printing of bar-coded shipping labels on printerdevices which are compatible with the client system on which the webbrowser is running, such as an HP-compatible laser printer. As depictedin FIG. 54, one of the NOC Servers, for instance, the Shipping Server,e.g., 21 t as depicted in FIG. 7, gets the Label Size from the CarrierLabel Specification 1250, the Label Layout from the Carrier LabelSpecification 1251, Label Data from the Shipper Database 1252, and theLabel Quality in Dots Per Inch (“DPI”) as set by the Server 1253, anduses this information to Generate the Label 1254.

The Server then creates, and causes the display on the client browser'sdisplay device of, a text string with a specified font face and in aspecified font size in an HTML table data cell with a specified width1255. If the client browser is using a 096 display device DPI, thedisplay device will display said text string in the HTML table data cellin a single line. If on the other hand, the client browser is using a120 display device DPI, the display device will display said text stringin the HTML table data cell in two lines.

In creating the display of the text string, the Server also sends amessage to the Shipper asking the Shipper to answer the followingquestion: do you see the text string displayed on your screen as asingle line or as wrapped text in multiple lines? The Server receivesthe Shipper's response and determines from the response whether theShipper's display device has displayed the text as a single line or aswrapped text in multiple lines 1256. If the text is displayed as asingle line, then the client browser 1258 display device DPI is 96.Otherwise, the client browser 1257 display device DPI is 120.

Next, the Server calculates the shipping label HTML image size in pixels1259 by multiplying the Carrier-specified label size from the CarrierLabel Specification times the client browser display device DPI asdetermined by the previous step.

Next, the System displays the generated label image in the clientbrowser 1260 with an HTML image tag and an HTML image size in pixels ascalculated in the prior step.

The client browser calculates the size of the label to be printed ininches by dividing the label HTML image size in pixels as calculated ina prior step by the client browser display device DPI 1261; the clientbrowser then prints out the label with the size calculated 1261.

FIG. 55 depicts a flow diagram of an exemplary embodiment of the aspectof the invention that provides printing of dimensionally accurateimages, such as dimensionally sensitive symbologies includingtwo-dimensional bar codes and other two-dimensional machine readablesymbologies. This aspect of the invention provides the printing of suchdimensionally accurate images on various types of printer devicesincluding among others HP-compatible laser printers. The printer devicescan be configured with remote computers, such as PC's, that will receivesignals to print the dimensionally accurate image over a communicationsnetwork such as the Internet. Each PC having a client browser orexecuting like software, and each PC being configured with apre-established Image Resolution that applies to the display device andthe printer device configured with the PC.

As depicted in FIG. 55, a computer, such as Server 20 t as depicted inFIG. 7, determines the Image Size 1350, the Image Layout 1351, anyrelevant Image Data 1352, and the Image Resolution in Dots Per Inch(“DPI”) or in any other measure of Image Resolution 1353. The Server 20t uses this information to Generate the Image.

Alternatively, the Image has previously been created; the Server 20 tdetermines from the Image, the Image Size 1350, the Image Layout 1351,any relevant Image Data 1352, and the Image Resolution in DPI or in anyother measure of Image Resolution 1353 (collectively referred tohereinafter as the “Image Characteristics”).

The Server 20 t determines the possible Image Resolution Categories andassociated values for client PC's 1354. Image Resolution Categories andassociated values include information such as the number of textstrings, and the length of and characteristics (font face, font size,and HTML table cell width) of each of the identified number of, textstrings that must be used to determine the Image Resolution of clientdisplay devices 1355-1356.

An HTML table cell width is fixed in that the physical width of thedisplay of the HTML table cell does not change depending upon theresolution of the client device; a text string comprised of charactershaving a particular font and font size has a scalable width, dependingupon the resolution of the client device resolution. Use of an HTMLtable cell to measure the resolution of client devices is not alimitation of the invention. In an alternative embodiment, a graphicelement other than an HTML table cell, having a fixed width, is used tomeasure the resolution of client devices.

The possible Image Resolution Categories and values are stored in thememory of the Server 20 t and updated on some basis. In an alternativeembodiment, the possible Image Resolution Categories and values areinput into the Server computer.

The Server 20 t then analyzes the Image Characteristics, and thepossible Image Resolution categories and/or values 1355, and creates theappropriate number of text strings and associated HTML table cells 1356.Each text string is created to have a specified font face, a specifiedfont size, and an associated HTML table cell with a specified width1356. The computer then causes the display of the text strings in theassociated HTML table cells on the remote client PC's display device1358.

In creating the display of the text string, the Server also sends amessage to the recipient PC asking the user to answer the followingquestion: is the first text string displayed on your screen as a singleline or as wrapped text in multiple lines? The Server 20 t receives theremote user's response and determines from the response whether theremote user's PC's display device has displayed each of the text stringsas a single line or as wrapped text in multiple lines 1256. The Server20 t then sets the PC's Remote Image Resolution for printing the Image1359 according to the results of the user's PC's display of the textstrings.

Next, the Server calculates the Remote HTML Image Size in pixels 1360 bymultiplying the Image Size times the PC's Remote Image Resolution asdetermined by the previous step.

Next, the Server displays the generated image on the display device ofthe remote PC 1361 with an HTML image tag and the Remote HTML Image Sizein pixels as calculated in the prior step.

The client browser of the remote PC calculates the size of the Image tobe printed (“Remote Print Image Size”) in inches by dividing the RemoteHTML Image Size in pixels by the Remote Image Resolution 1362; theclient browser then prints out the Image with the Remote Print ImageSize 1362.

In one embodiment of the invention, instead of printing a shipping labelat the Shipper's printer, a Package Number 1120 is displayed online on aPackage Number Screen with notification that the label will be printedat a shipping location previously designated by the Shipper. FIG. 56depicts an exemplary embodiment of a Package Number Screen. The Shippercan Void the Package Label at this point by clicking the Void Packagebutton 1121. The Shipper can request shipping of a new parcel byclicking the “New Package” button 1122 or can indicate completion ofshipping instructions by clicking the “Done” button 1123.

FIG. 57 depicts an exemplary embodiment of a Generate Shipping LabelScreen in an exemplary simplified Internet embodiment of the invention.The Shipper is given instructions 1125 as to how to print the label.Clicking the “Generate Label” button 1124 causes the bar-coded label tobe generated.

FIG. 58 depicts an exemplary embodiment of a Print Label Screen in anexemplary simplified Internet embodiment of the invention. At the top ofthe Screen, an instruction 1130 is displayed to scroll to the bottom ofthe screen for instructions. The generated label 1131 is displayed inthe main body of the screen. Instructions for printing the label 1132are displayed at the bottom of the screen. Clicking the “Print Label”button 1133 (visible only for supported web browsers) will cause thelabel to be printed. Clicking the “Done” button 1134 will close the webbrowser window.

Returning to the exemplary eCommerce embodiment, if the Seller choosesto ship a specified package, e.g., by clicking on the Ship button 444 asdepicted in FIG. 50, the System requests the Seller to input informationto e-mail a notification to the Buyer that the package is being shipped.FIG. 59 is a graphic representation of an exemplary embodiment of a SendShip Notification screen (67, as depicted in FIG. 10E). In one eCommerceembodiment, this information is automatically prepared by the System andan e-mail (e.g., 70 as depicted in FIG. 10E) is automatically sent tothe Buyer (80, e.g., FIG. 10E) when the Seller ships the package. In oneembodiment, the Seller completes the information in this screen only ifthe Seller ships the package with a Carrier or a service that is notsupported by the System.

In an exemplary FIG. 60 depicts an exemplary E-Mail Others “Messages”pop-up Window in an exemplary simplified Internet embodiment whichallows the Shipper to identify the “To” or “cc” status of the desirednotification 1101 using a drop down menu activator 1102 and which allowsthe user to enter each e-mail recipient's Name 1103 and E-Mail Address1104. FIG. 60 depicts two Recipients 1107 and 1108; the screen isexemplary and is not a limitation of the invention.

Returning to the exemplary eCommerce embodiment, when the Seller choosesto ship a specified package, the System prepares and displays a Ship aPackage Summary report (68, FIG. 10E) an exemplary embodiment of whichis depicted in FIG. 61.

If the Seller/Shipper ships packages using UPS, the Seller will need torun UPS End of Day processing (71, FIG. 10E) at least once each day apackage is shipped using UPS. FIG. 62 is an exemplary embodiment of theUPS End of Day screen. The System provides instructions 470 and aPerform End-of-Day button 471. The System also provides Reprintinstructions to reprint a driver record from a previous End-of-Dayprocess 472 and a Find Driver Record button 473.

FIG. 63 is a graphic representation of an exemplary embodiment of aReprint Driver Record Screen that lists prior driver records 480, eachrecord provides a Reprint button 481 which when clicked will reprint thedriver record (72, FIG. 10E).

After the Seller has completed printing the label, the Seller must givethe package to the Carrier (73, FIG. 10E) so that it can be deliveredvia the Carrier (74, FIG. 10E).

The System provides complete tracking and reporting capabilities forpackages shipped through it, and for packages for which a Carriertracking number is known as described below and as disclosed in U.S.Provisional Patent Application Ser. No. 60/170,186, the disclosure ofwhich has previously been incorporated for all purposes herein byreference.

FIGS. 64A-1, 64A-2, 64B-1 and 64B-2 are System interactivity data andlogic flow diagrams depicting an exemplary eCommerce embodiment of theprocess by which the System completes the information necessary to shipa package. References in the explanation and description of FIGS. 64A-1,64A-2, 64B-1 and 64B-2 to the Buyer mean to the Buyer and the Buyer'scomputer 8-2; references to the Seller mean to the Seller and theSeller's computer 8-1; references to the System mean the System servers,20 a-20 n (the database servers) and 21 a-21 z (the other Systemservers); references to the System database mean to the entire logicalSystem database 22.

The Seller eCommerce Preference setup Processes 231 through 239 havebeen previously described herein above. After the Seller has completedsetting up eCommerce preferences, and after the Seller is notified of asale, the Seller enters the System and prepares to enter Buyerinformation by clicking on the Buyer information submenu option 501. TheSystem then displays a Buyer Information screen 502 to the Seller. TheSeller then enters Buyer information and clicks the Next button 503. TheSystem responds by displaying the Item and Cost screen 504. The Sellerenters the item and cost information and sends the information to theSystem 505.

The System uses the information provided by the Seller to create a newpackage record in the System database and sets the status of the packageto “waiting for buyer's response” 506. The System prepares and sends ane-mail to the Buyer requesting information to complete the shipment andincluding a URL hyperlink to the System web site page that is availableto intake the Buyer's information, the URL containing a System packagetracking number for the specified package 507. The System also preparesand sends an e-mail to the Seller informing the Seller that the e-mailhas been sent to the Buyer 508.

The Buyer upon receipt of the System e-mail, uses a web browser tonavigate the URL in the System e-mail and enter the System 509. TheSystem retrieves the System package tracking number from the URLprovided by the user's browser to access 510 and retrieve 511 thepackage information from the System database. The System provides theBuyer with an introduction and instructions to complete the process 512.If the Buyer chooses to proceed, the Buyer clicks the Next button 513.The System then requests Buyer shipping information 514. The Buyercompletes the Buyer shipping information and clicks the Next button 515.The System accesses 516 and retrieves 517 from the System databaserating information, including the Seller's preferences. The System usesthe rating information and prepares and displays for the Buyer amulti-carrier, multi-service shipping cost comparison Graphic Array 518.The Buyer selects a Carrier/Service entry from the Graphic Array to shipthe package 519. The System verifies the information and requestspayment information from the Buyer in accordance with the Seller'spreferences 520. The Buyer selects a payment method, enters paymentinformation and Sends the information to the System 521. The Systemstores all Buyer information and associates that information with thepackage, and updates the package status to “buyer has replied” 522. TheSystem sends an e-mail to the Seller notifying the Seller that the Buyerhas replied 523. The System in some embodiments sends an e-mail to theBuyer notifying the Buyer that the System has informed the Seller thatthe Buyer has replied 524.

The Seller requests a Shipping Log of “Today's Packages” 525. The Systemaccesses the System database 526 to retrieve 527 a Shipping Log of theSeller's packages that need to be processed. The System displays theShipping Log to the Seller 528. The Seller locates the package to whichthe Buyer responded and clicks the Ship button 529. The System displaysthe Shipping screen to the Seller 530.

FIGS. 65A and 65B represent a database schema diagram that depicts anexemplary embodiment of tables in which data is stored by the Systemregarding a particular package and a particular Seller's Account, andfrom which information is retrieved in order to facilitate the shipmentof a package. The database schema depicted in FIGS. 65A and 65B providesan Account User table 251, a Users table 252, an Account UserConfiguration table 253, a Carrier Account table 254, an Account table255, an Account and Carrier Account table 256, an Address table 257, aSite Type table 258, an Account and Site Type table 259, an Account andSite table 260, and a Site table 270, all of which were previouslydescribed herein above with respect to FIGS. 33A and 33B. The databaseschema with respect to package information further provides the PackageTable 261. The Package Table 261 contains for each package, among otherthings, a Package OID (a pointer) 261-1, the actual weight 261-2, length261-3, width 261-4, height 261-5, System package tracking number 261-6,site type ID 261-7, Site OID (a pointer) 261-8, Account number 261-9,User ID 261-10, From contact name 261-11, From address 1 261-12, Tocontact name 261-13, To address 1 261-14, Bill contact name 261-15, andthe Bill address 1 261-16.

F. TRACKING

The tracking features described below apply similarly to both anexemplary simplified Internet embodiment and to an exemplary eCommerceembodiment of the invention.

1) User Requested Tracking

In order to track a particular package using the System, a Shipperidentifies a tracking number for that package to the System and requeststhat the System report the status of the package. Two types of trackingnumbers are used to track packages: 1) Carrier tracking numbers and 2)System tracking number.

Each Carrier assigns each package a tracking number that uniquelyidentifies each package and which is used to trace packages as thepackage moves through the particular Carrier's system to the package'sdestination. The Shipper or the package recipient uses the trackingnumber for a particular package to track, locate, and verify delivery ofthe particular package.

A System tracking number is a unique number generated internally by theSystem to identify a particular package shipped using the System. TheShipper inputs the Shipper's Parcel Specifications for the SubjectParcel. Using each Shipper's Parcel Specifications, the System isprogrammed to access databases containing information about eachsupported Carrier. Each supported Carrier has a unique rating schedule,delivery and pickup rules and schedules, and certification requirements(the “Carrier Rules”). The System is further programmed to apply eachsupported Carrier's Rules to each Shipper's Parcel Specifications forthe corresponding Subject Parcel. The System provides an online displayof a Dynamically Dimensioned Multi-Carrier, Multi-Service Graphic Arrayas depicted, e.g., in FIGS. 36 a and 46 described above.

The Shipper in this case uses a user input device to pick the preferredCarrier, by for instance placing the cursor of the Shipper's PC on thedisplayed Carrier cell entry, e.g. 1065 a, in the Graphic Display asdepicted in FIG. 36A and clicking the Shipper's user input device (the“Selected Carrier”).

As a result of the Shipper selecting a Carrier cell entry in the GraphicDisplay to ship a package, the System assigns the package a Systempackage tracking number and adds a record containing all of thepertinent information about the package to the System database 22.Following are exemplary Shipping tracking numbers: MAGGY841VRY50;MAGGY84B496RF; MAGGY84XOFJ45. In one embodiment, the System TrackingNumber is based on a Base-33 number system. The characters availableare: Zero (0) through nine (9) and A through Z excluding “I” (i), “L”(l), and “O” (o). Each letter represents a value, as depicted in thetable below:

-   -   A=10 F=15 M=20 S=25 X=30    -   B=11 G=16 N=21 T=26 Y=31    -   C=12H=17 P=22 U=27 Z=32    -   D=13 J=18 Q=23 V=28    -   E=14 K=19 R=24 W=29        Each System Tracking Number is 13 alphanumeric characters.        Position 1 is the letter ‘M’. Positions 2-7 are a System Account        number. Positions 8-12 are a five-digit ID. Position 13 is a        Check Digit.

To calculate the Check Digit, the System performs the followingsteps: 1) Consecutively multiply the numeric value of each of positions2-7; 2) Consecutively multiply the numeric value of each of positions8-12; 3) Add both results; 4) Divide by 31; 5) Convert the remaindervalue to a Base-33 number. The converted value is the Check Digit.

Referring to FIG. 5 once again, when a Shipper/User ships a packageusing the System, one or more of the System's Servers, e.g., 21 a-21 ncreate a new System tracking number. When a new System tracking numberis created, one of the System's Database Servers, e.g., 20 a-20 n, addsa new package record with the newly created System tracking number to aPackage Table 28.

The Package Table 28 resides in the System database 22 and containspackage records for System processed packages. An exemplary embodimentof the Package Table contains the following information: 1) PackageTracking State ID; 2) Package Shipping State ID; 3) Actual DeliveryTime; 4) Delivered To information; 5) Shipping Date; 6) Carrier TrackingNumber; 7) System Tracking Number; 8) Carrier ID; 9) Actual PackageWeight; 10) Service Description; and 11) Package OID. The content ofthese fields are described further below.

The Package Tracking State ID specifies the tracking state of thepackage. In an exemplary embodiment of the invention, there are fourdifferent tracking states: 1) Null (New Packages or Shipped Packages);2) Manifested (at the end of each day, package information is moved tothe Package History Table for tracking purposes); 3) In Transit (TheCarrier has picked up packages); 4) Delivered (Packages have beendelivered to the shipping destination).

The Package Shipping State ID specifies the shipping state of a package.In an exemplary embodiment of the invention, there are two differentshipping states: 1) Shipped (New Packages or Shipped Packages); 2)Manifested (at the end of each day, package information is moved to thePackage History Table for tracking purposes).

The Actual Delivery Time specifies the Date/Time that the package wasactually delivered. The Delivered To information identifies the personor place to which the package was delivered (e.g., left withreceptionist, receptionist front desk, or guard). The Ship Datespecifies the date on which the Carrier picked up the package. TheCarrier Tracking Number identifies the Carrier-specific package trackingnumber. The System Tracking Number specifies the unique Package trackingnumber internally generated by the System (each System tracking numbercorresponds to exactly one Carrier-specific tracking number). TheCarrier ID specifies an identification code for the particular Carrier.The Actual Package Weight specifies the actual weight of the package asopposed to the billed weight. The Service Description describes the typeof services used to ship the package e.g., Overnight, 3 Day Ground,Second Day Air, etc. The Package OID contains a Globally UniqueIdentifier (“GUID”) for each package.

When the System creates a new package record, the record remains in thePackage Table 28 during an initial period of time, for example, thefirst day during which the record is created, so that the Shipper/Usercan modify information about the package or void the package record asappropriate. In an exemplary embodiment of invention, the Systemperforms certain processing on a periodic basis, such as at the end ofeach business day. This type of processing is referred to herein as “EndOf Day” processing. In an exemplary embodiment of the invention, during“End of Day” processing, the System removes all new package records fromthe Package Table 28 and moves the records to a Package History Table 29which also resides on the System Database 22. In an exemplaryembodiment, Package History Table 29 records contain the same datafields as described above regarding Package Table 28 records.

FIG. 68 is a graphic representation of a Shipper online user inputscreen that is displayed on the Shipper's display screen 10. If aShipper/User wants to track a particular package, the Shipper/Userenters the tracking number that identifies the particular parcel packageof interest in the “Enter tracking number” field 2035. It should beunderstood by those with ordinary skill in the art that the User may besomeone other than the Shipper. For instance, the User may be aRecipient who wishes to track a package being sent to the user. Once theUser has entered a tracking number, the User submits a request to trackthe particular package identified by clicking on the Submit button 2036.

FIG. 69 is a logic flow diagram that depicts the high level logic fortracking the status of a particular package. The User enters 2018 a and2018 b a tracking number 19 in the tracking number field 2035 (as wasshown in FIG. 68). The System first validates 2050 the tracking number19. The System performs the validation process by attempting to accessthe record on the System database 22 that is associated with thetracking number 19. To do this, the System requests that a Systemdatabase server, e.g., 20 a (as depicted in FIG. 5) locate and retrievethe package record that is associated with the tracking number 19. TheSystem database server, e.g., 20 a as depicted in, e.g., FIG. 5, usesthe entered tracking number 19 to search the System database 22 tolocate and retrieve the specified package record. In one embodiment, theSystem database server, e.g., 20 a as depicted in, e.g., FIG. 5, isprogrammed to perform database accesses using Sequel 7.0.

Through the validation process, the System determines whether thetracking number 19 is a System tracking number or a Carrier trackingnumber. Below are examples of Carrier tracking numbers.

UPS—1z8595610344113190

Airborne—3918984344

FedEx—811152682326

USPS—ej585489546us

Yellow Freight—2100003475

If a user enters a Carrier tracking number as the tracking number 19,then depending upon the status of the package, or the number of timesthat the package was tracked, there may be no information in the Systemdatabase 22 for the Carrier tracking number. In such a case, the Systemthen uses algorithms provided by each Carrier to determine the Carrieridentification.

If the System determines that there is information about the package onthe System database 22, then the System analyzes the Package ShippingState. If the Package Shipping State of the retrieved record is“Manifested” or “In Transit” and the Package Tracking State is not“Delivered”, then the System prepares to track the package using theappropriate Carrier system. If the Package Shipping State of theretrieved record is “Delivered”, or other final status, then the Systemreports the status of the package to the user.

If the tracking number 19 is a valid System tracking number, then theSystem extracts the Carrier's tracking number and Carrier's ID from thepackage record retrieved from the System database 22 before issuing arequest 2054. Otherwise, if the tracking number 19 is a Carrier trackingnumber, then the System extracts the Carrier's ID from the packagerecord before issuing a request 2052 to the Carrier's Internet system.The System uses the Carrier's ID to retrieve from the System database 22the Internet URL for the Carrier's Internet web site. The URLinformation is configurable.

Returning for a moment to FIG. 5, using the Carrier's Internet URL, theSystem then makes an HTTP connection to the Carrier's web server, e.g.,23-2, 24-2, 25-2, 26-2, or 27-2, using the URL information for theparticular Carrier's web server. Depending upon the Carrier, theSystem's 1 request and report interface with the Carrier's web server isprogrammed in HyperText Markup Language (“HTML”) (e.g., 24-1, 25-1,27-1), Extensible Markup Language (“XML”) (e.g., 26-1), or both HTML andXML (e.g., 23-1). FIG. 66 depicts an exemplary XML formatted request forsubmitting a tracking request to a Carrier. FIG. 67 depicts an exemplarysuccessful tracking response, also in XML format, returned by theCarrier.

Then, as depicted in FIG. 69, the System transmits the Carrier'stracking number over the HTTP connection (2052 or 2054). The Systeminstructs the Carrier's web server as to what information is requestedbased on the connection made using the URL.

If the Carrier's web server successfully responds 2055 to the System's 1tracking request, the System disconnects from the Carrier's web serverand parses the response data. Some Carriers' response data containsunnecessary text information. The System strips out all of theunnecessary text in order to parse the relevant information.

If the System database 22 does not have any previous record of thepackage, such as would be the case if the package had not been shippedusing the System shipping application, then the System does not storeany data about the package in the Package Table or the Package HistoryTable.

Otherwise, the System then updates the System database 22 and reportsthe information to the Shipper/User 2056. If the package is reported asdelivered, the System populates the Package History Table 29 in theSystem database. As was previously mentioned, in an exemplaryembodiment, Package History Table 29 records contain the same datafields as described above regarding Package Table 28 records.

If on the other hand, the Carrier's Internet web server returns anunsuccessful report from test 2050, the System reports the failure 2051to the User. FIG. 70 is a graphic representation of an exemplaryunsuccessful tracking report to the User. The Tracking Failure ReportScreen as depicted in FIG. 70 informs the User that the System wasunable to track the package 2060 and displays 2061 the package trackingnumber 19 that the User previously entered. The Tracking Failure ReportScreen asks the User to verify the accuracy of the tracking number andto specify a Carrier by name 2062. The Tracking Failure Report Screenprovides a pull down menu button 2063, that when clicked, displays alist 2064 of the supported Carriers. The user enters a new trackingnumber 19 in the tracking number field 2035 and specifies the Carrier byhighlighting one of the Carriers displayed in the list 2064. The usersubmits the request by clicking on the Submit button 2036 (covered bythe pull down selection list 2064 in FIG. 70).

If the Carrier's system successfully returns tracking information, thenthe System displays the package's current status. As depicted in FIG.71, if the package has a “Delivered” status, the System reports theStatus 2071; status as of Last Scan including date time and location2072; Delivered To location 2073; Delivery Date 2074; Delivery Time2075; Delivery Location 2076; Signed by 2077; Carrier Name 2078; Service2079 and Tracking Number 2080.

Status 2071 reports the Delivery Status, also referred to as the Track,or Tracking, State. Last Scan 2072 reports Last scan information for theparticular package. When a package is moved from one location toanother, the label of the package is scanned according to each Carrier'sprocessing requirements. Also, many Carriers scan package labels whenpackages are received by the recipients. Delivered To 2073 reports theperson or place to which the package was delivered (e.g., left withreceptionist, receptionist front desk, or guard). Delivery Date 2074reports the date on which the package was delivered. Delivery Location2076 reports, for most carriers, the city, zip code, and stateinformation for the location to which the package was delivered.However, for some carriers, such as UPS, the delivery location reportswhere the package was dropped off (e.g., front porch, front door).Signed By 2077 reports the name of the person who signed the packageafter receiving it. Carrier 2078 reports the name of the Carrier thatdelivered the package. Service 2079 reports the type of shipping service(i.e., Ground). Tracking Number 2080 reports the System tracking numberor carrier tracking number entered by the User.

The User is invited to enter another tracking number 19 in the trackingnumber field 2035 and click the Submit button 2036 to submit the nexttracking request.

As depicted in FIG. 72, if the package has not yet been delivered, theSystem reports the information available, e.g., the Status 2071, LastScan 2072, Carrier 2078 and Tracking number 2080. In such a case, theSystem asks the User if the User want to be notified when the identifiedpackage is delivered 2090. The System provides the User with inputfields to register to receive, and have sent, e-mail notification afterthe package is delivered. A user can enter up to three names, 2091, 2093and 2095, and up to three e-mail addresses, 2092, 2094, and 2096, toreceive the delivery confirmation. The User submits the e-mailnotification (with message 2097) by clicking on the Submit button2036-1.

If the User completes the e-mail notification input fields with at leastone e-mail name and address, e.g., 2091 and 2092, the System creates anentry in a Track Response Table 30 which is a table contained in theSystem Database 22 as depicted in FIG. 5. The Track Response Table entrycontains the tracking number 19 earlier specified by the User anddisplayed 2080 in the Tracking Report Screen depicted in FIG. 72. TheSystem uses the Track Response Table 30. The System performs AutomaticTracking for all of the package tracking numbers contained in the TrackResponse Table 30 at the time that the Automatic Tracking procedure isexecuted. Automatic Tracking is described in more detail below.

The User can then enter another tracking number 19 in the trackingnumber field 2035 and submit the new request by clicking on the Submitbutton 2036-2. When the Carrier delivers the package, the System detectsthe delivery through one of several ways, as will be further explainedbelow, and then sends e-mail with a link to the web page with the mostup to date package status.

In an alternative embodiment, if the tracking number 19 is a Carriertracking number, the Server will validate the Carrier tracking number isa valid tracking number. If the Carrier tracking number is not a validnumber, the Server will return an invalid tracking number error. If theCarrier tracking number is a valid number, the Server will not attemptto match the number to a manifested package; the Server will track thepackage using the particular Carrier's Internet tracking routine; andwill return the tracking response to the Web Client of the requestingShipper/User.

In an alternative embodiment, if the tracking number 19 is a Systemtracking number, then the System validates the System tracking number toensure that it is a valid System tracking number. If the System trackingnumber is not a valid tracking number, the Server will return an invalidtracking number error. If the System tracking number is a valid trackingnumber the Server queries the System database 22 to find the Carriertracking number which corresponds to the System tracking number. If nopackage record is found for the System tracking number, then the Serverwill return an error to the Web Client of the requesting Shipper. Theerror message will indicate that no package record was found; it willrequest the user to verify that the tracking number was from a packagewhich had been dropped off notify the user that a package be tracked onthe same day it shipped. If the package record is found and the actualship date is the same as the current date, the Server will return anerror to the Web Client of the requesting Shipper indicating that theuser/Shipper cannot track the package on the same day it is shipped.

In this alternative embodiment, once the Server has identified theCarrier tracking number, the Server will track the package using theCarrier's Internet tracking routine. If the tracking response from theCarrier's Internet tracking routing indicates an error, the Server willmake another attempt to track the package through the Carrier's Internettracking routine. If the second tracking request results in an error,the Server will notify the Web Client of the requesting Shipper that theCarrier is unable to track the package, and will log a tracking requesterror containing the Error Log number, the System tracking number, theCarrier tracking number, the time and date the tracking requestoccurred, the error response reported by the Carrier, and the AccountName of the user/Shipper making the tracking request, if thatinformation is available.

If, on the other hand, the Carrier returns a valid tracking response,the Server will update the package status in the Server Database withthe tracking response and will return the detailed package informationto the Web Client of the requesting user/Shipper from the SystemDatabase as described below.

If the user supplied a Carrier tracking number, the Web Client willdisplay the basic tracking information provided by the particularCarrier's Internet tracking function. In one embodiment of theinvention, when the user provides a Carrier tracking number to track apackage, the user/Shipper's Web Client requires the user/Shipper toidentify the Carrier.

If the user/Shipper provides a System tracking number, then if theuser/Shipper is logged on to the account, or otherwise enters validlogon information, that information must correspond to the Account whichshipped the package. In that case, the user/Shipper's Web Client willdisplay the following information: System tracking number; recipientaddress; drop off location; Carrier and service; Carrier tracking numberif available; actual ship date if available; delivery address ifavailable; delivery location if available; delivery date if available;delivery time if available; signed for by information if available;package rate; package weight; package dimensions; packaging; customerreference information; all scan activity.

If on the other hand, the user/Shipper is not logged on to the account,fails to enter valid logon information, or is logged on to an Accountwhich does not correspond to the Account which shipped the package, theuser/Shipper's Web Client will display the following information: Systemtracking number; recipient contact name; recipient company name; Carrierand service; Carrier tracking number if available; actual ship date ifavailable; delivery address if available; delivery location ifavailable; delivery date if available; delivery time if available;signed for by information if available; package weight; customerreference information; all scan activity.

2) Automatic Tracking

Automatic Tracking of packages with Priority Delivery Notification isperformed when the package meets the following criteria: the package isa manifested package; the package was shipped using Priority DeliveryNotification; The actual ship date of the package is the earlier thanthe current date; the package does not have the status of Delivered orLost.

Automatic Tracking of a particular package can be requested by the User,as depicted in FIG. 72 and as was described above

If the package fulfills all of the above-described automatic trackingcriteria, the System places a record in the Track Response Table 30 andthereafter tracks the package on some regular periodic time interval,for example, every four hours beginning at a staggered start time. Thestart time is determined randomly and is staggered to occur at regularintervals every four hours.

The System tracks the package using the specified Carrier's Internettracking routine as was previously described above. If the Carrier'sInternet tracking routine returns a tracking response that the trackingrequest is an error, the Server will track the package at the nextstaggered tracking time. If the second tracking request response is alsoan error, the Server will track the package at the next scheduled fourhour interval. If the third tracking request fails, the Server will loga tracking request error containing the following information: error lognumber; System tracking number; Carrier tracking number; time and datethe tracking request occurred; and the error response from the Carrier.In the event that the third tracking request fails, the Server willissue an Automatic Tracking Alert, for instance, to System Support,containing the error log number.

If the tracking request results in a successful tracking response, theServer will update the package status in the Package History Table 29 inthe System Database 22 with the tracking response information. If thepackage status returned is Delivered, the Server will send deliverynotification via e-mail to the notification address(e), e.g., 2091-2096as depicted in FIG. 72, as previously supplied by the Shipper/User. Fora Delivered package, the Server will update the Package History Table 29in the System Database 22 to indicate that the package has beendelivered, that a delivery notification e-mail has been sent, and thedate and time that the e-mail was sent.

If the manifest package was shipped without Priority DeliveryNotification, then on any day after the actual ship date, as long as thestatus of the package is not Delivered or Lost, the System will trackthe package every day at a non-peak period. If the tracking response isan error, the Server will not attempt a second tracking request. If thetracking response is successful, the System will update the packagestatus in the System Database 22 with the tracking response information.

The System will verify that all packages with a status of Delivered weredelivered within the guaranteed delivery time. For each Deliveredpackage for which delivery was not made with the guaranteed deliveredtime, the Server will generate a Delivery Exception containing thefollowing information: Carrier account number for the Drop Off Location;Carrier tracking number; date of shipment; complete destination addressinformation; delivery exception ID number.

In one embodiment of the invention, there are four types of scripts, orprocedures, that run regularly to update the Package History Table 29and the Track Response Table 30 in the System database 22: 1) Track AllScripts, 2) Track Inbound Script, 3) Inbound Confirmation Mail Scriptand 4) Delivery Confirmation Script. Each is described further below.

Track All Scripts are run on a regular basis. There is a Track Allscript for each Carrier (e.g., FedEx, UPS, Airborne, and YellowFreight). Each Track All script executes a set of instructions thatenumerate the package records in the Package History Table 29 to getupdated information from a specific Carrier's database. If a Systemtracking number has a delivered tracking state, then the next time auser tries to get tracking information for this particular trackingnumber, the System will not need to connect to the Carrier's web serverto get the package status information.

Track Inbound Script is run on a regular basis. Track Inbound Scriptsearches the Track Response Table 30 and enumerates all entries in thetable to get updated information from multiple Carriers' databases. If atracking number has a delivered tracking state, then Users are notifiedvia e-mail that their packages have been delivered. Also, if thetracking number is a System tracking number then the Package HistoryTable 29 gets updated with this delivered tracking state information foroptimization purposes. By updating the Package History Table 29, theSystem does not need to re-connect to carriers' web servers to getinformation about a package that has been already delivered.

Inbound Confirmation Mail Script is run on a regular basis. It searchesthe Track Response Table 30 for packages that have a delivered trackstate. When the script finds delivered packages for Users who requestedto receive e-mail notifications, it sends e-mail notifications to themwith delivery information.

Delivery Confirmation Script is run on a regular basis. It searches thePackage History Table 29 and enumerates all entries in the table forwhich the User has requested delivery notification when the subjectpackage has been delivered to destination. When the script findsdelivered packages in the Package History Table 29 for Users whorequested to receive e-mail notifications, it sends e-mail notificationsto them with delivery information.

3.) Counter Manifest System (CMS) Tracking

As an alternative to using an Internet embodiment of the invention, auser can track packages by using the counter Manifest System CMS featureof the invention. In such an embodiment, CMS is a standalone-dedicatedsystem that uses a connection to one of the System's servers (the “CMSServer”) to track packages. CMS can be connected to one of the Systemservers in many different ways, including among others, DSL dial-up,ISDN dial-up, Modems, T1 line, Hughes VSAT link or other communicationssystems.

In the CMS environment, a company maintains a connection for the CMS tothe CMS Server to track packages for customers. The CMS User trackpackages for the CMS User's customers by entering a tracking number inthe CMS tracking page. CMS tracking allows a customer to register for adelivery confirmation to receive e-mail notifications when packages aredelivered. Also, customers can register using the System's Internetembodiment to receive inbound delivery notifications for the packagesthat are shipped using the CMS.

FIG. 73 is a graphic representation of an exemplary CMS online userinput screen. The User inputs a tracking number 19 in the input trackingnumber field 2100 and submits a request to the System to track thepackage associated with the input tracking number 19 by clicking on the“Track” button 2102 or the “Find Package” button 2101.

FIG. 74 is a graphic representation of an exemplary CMS display screenthat reports a successful tracking result 2103. After reading thetracking report, the User can request that another package be tracked byclicking the “Track Another” button 2104.

FIG. 75 is a graphic representation of an exemplary CMS error trackingreport display screen. The tracking number 19 is displayed with an errormessage 2105. The user can request that another package be tracked byclicking the “Track Another” button 2104.

4.) Manifest and Inbound Tracking

A User can register with the System to establish a shipping account.Once a User has established an account, the System will record in theSystem database 22 information for every package shipped under theUser's account. The information contained in the System database 22under the User's account is referred to as the User's Shipping Log.

The System provides the User with online capability to requestinformation about the User's Shipping Log. FIG. 76 is a graphicrepresentation of an exemplary embodiment of a “My Tracking” Screen. Onthe viewer's left side of the My Tracking Screen display, a “My Trackingsubmenu 2110 is provided to allow the User to select options. Byclicking on and highlighting one of the My Tracking submenu 2110options, the User can select to view the User's Account's Shipping Log2111, to View Inbound Packages 2112, to Add Inbound Packages 2113, andto indicate Tracking Preferences 2114. The User can also input atracking number 19 into the Quick Track input field 2115 and requestthat the System track the identified package by clicking the “go” button2116.

FIG. 77 is a graphic representation of an exemplary embodiment of aShipping Log Screen. A logged on registered User enters this displayscreen by clicking on the My Tracking submenu 2110 User's Account'sShipping Log option 2111. If the User is both logged on and registered,then in response to the User clicking on the My Tracking submenu 2110,User's Account's Shipping Log option 2111, the System presents aShipping Log Screen with certain selection criteria. In the embodimentdepicted in FIG. 77, the System initializes selection criteria fieldswith certain default values. For instance, the Shipping Log will searchthe system database 22 for the name of the individual to whom theparticular account belongs and displays the name of the person 2109.Further, the Shipping Log application will search the System database 22for all packages shipped under the User's account that conform to thecriteria specified in the input fields of the FIG. 77 screen.

The Shipping Log Screen provides for User selection of the Type ofpackage, e.g., “All Packages” from the Display option 2118 and Displayoption pull-down menu button 2117; “For the Past” time period 2119 witha pull-down menu button 2120, e.g., for the past “Month” during whichpackages were shipped; and “Sort By” 2121-2122 which allows the User toselect the order of the Shipping Log report entries.

In response to the Shipping Log request, the System creates a list anddisplays an online Shipping Log record for the packages shipped underthe User's account and which fit the selection criteria. For each suchpackage, the System displays: the Status of the package 2125 and thetracking number 2080, the name of the shipper 2126, the Carrier Service2127, the name of the Carrier 2128, the Ship Date 2129, and the DeliveryDate and time 2129-2130. If the User wants more information for aparticular package in the Shipping Log, the User highlights theappropriate record in the list and clicks the “Details” button 2124. An“Update View” button 2123 is also provided.

FIG. 78 is a graphic representation of an exemplary embodiment of aDetailed Shipping Log Entry Screen which is displayed if the Userhighlights the appropriate record in the Shipping Log list and clicksthe “Details” button 2124. The System displays the Shipping Log date andtime 2140, the System tracking number 2141, the estimated weight of thepackage 2142, the billed weight of the package 2143, the Packaging type2144, the Carrier and Service 2145, a description of the goods shipped2146, the shipping status 2071, the Carrier tracking number 2080, theShipped Date 2147, the Expected data of arrival 2148, the Last Scaninformation 2072, the Recipient's name and address 2149, the Return nameand address 2150, the Ship from location 2153, the base shipping servicecharge 2151, and the total shipping charge 2152.

FIG. 79 is a graphic representation of an exemplary embodiment of adetailed “Quick Track” result screen which displays the same type ofinformation described above for FIG. 78. The way that a User obtainsthis display is to enter a tracking number 19 into the Quick Track inputfield 2115, and by then clicking on the “go” button 2116.

A registered logged on User can view inbound packages if the User firstidentifies to the System package tracking numbers for each of thepackages the status of which the User is interested in monitoring. FIG.80 is a graphic display of an exemplary embodiment of an “Add InboundPackages” Screen. The User requests this screen by clicking on the “AddInbound Package” option 2113 of the “My Tracking” submenu 2110. The Userinputs identification information, such as the tracking number 19 in theinput tracking number field 2035, the Carrier 2128, and the Order/Item2161. The User can also specify that the System is to provide e-mailnotification 2162 with an e-mail message 2163. By clicking on the“E-mail Others” button 2164, the User can request an “E-mail Others”screen providing input similar to that, items 2091-2097, and 2036-1,described above for the tracking screen depicted in FIG. 72. By clickingon the “Add” button 2165, the User requests that the record identifiedin the User's input be added to a list for that User of Inbound Packagesto be monitored. A “Cancel” button 2166 is also provided.

Once the User has input the identification information for the packagesthe status of which the User wants to monitor, and added all suchrecords to the User's Inbound Tracking List, the User can then view thestatus of those identified Inbound packages. To do so, the user clickson the “View Inbound Packages” option 2112 of the “My Tracking” submenu2110. FIG. 81 is a graphic representation of an exemplary embodiment ofa “View Inbound Packages” Summary Screen. Similar to the Shipping LogScreen as discussed above in relation to FIG. 77, the View InboundPackages Summary Screen displays information about packages identifiedby the User as Inbound Packages. As depicted on FIG. 81, the User canspecify reporting criteria such as Display limitations 2117-2118, andsorting requests 2121-2122. The User can request details about aparticular package by highlighting the reporting line on the screen andclicking the “Details” button 2124. The User can delete a particularpackage from Inbound Package Tracking by highlighting the reporting lineon the screen and clicking the “Delete” button 2170. An “Update View”button 2123 is also provided.

FIG. 82 is a graphic representation of a View Inbound Packages DetailScreen. The type of information displayed on this screen is similar tothe type of information described with respect to the Shipping LogDetail Screen as depicted in FIG. 78 and discussed above.

ILLUSTRATIVE EMBODIMENTS

Although this invention has been described in certain specificembodiments, many additional modifications and variations would beapparent to those skilled in the art. It is, therefore, to be understoodthat this invention may be practiced otherwise than as specificallydescribed. Thus, the embodiments of the invention described hereinshould be considered in all respects as illustrative and notrestrictive, the scope of the invention to be determined by the appendedclaims and their equivalents rather than the foregoing description.

1. A shipping management computer system comprising at least onecomputer device that is programmed for: collecting from a second user, arequest that a first user ship a particular parcel to a destination tobe designated by the second user; according to the request by the seconduser, collecting, from the first user via a first set of interactiveaccesses to the shipping management computer system by a first computerdevice, a set of information corresponding to the request comprising:(A) parcel specifications for shipping the particular parcel to thedestination to be designated by the second user, (B) an origin addressassociated with the first user from which the particular parcel would beshipped, and (C) shipping preferences for shipping the particular parcelto the second user; collecting, from the second user via a second set ofinteractive accesses to the shipping management computer system by asecond computer device, a set of recipient information corresponding tothe request comprising: (A) a destination address to which theparticular parcel is to be shipped by the first user, (B) anidentification of a carrier to be used in shipping the package to thedestination address, and (C) a delivery service by which the carrier isto ship the package to the destination address; calculating a shippingrate corresponding to the request, according to the set of recipientinformation collected from the second user and according to the set ofinformation collected from the first user, to be charged for having thecarrier ship the particular parcel from the origin address to thedestination address via the delivery service; and displaying theshipping rate to a display device selected from a group consisting of:(A) a first display device that is in communication with the firstcomputer device, and (B) a second display device that is incommunication with the second computer device, wherein said shippingrate is calculated according to: (1) the parcel specifications and theorigin address input by the first user, and (2) the destination address,the selection of the carrier, and the selection of the delivery serviceinput by the second user.
 2. The shipping management computer system ofclaim 1, said at least one computer device being further programmed for:generating a shipping label for the delivery service and the carrier toship the particular parcel from the origin address to the destinationaddress; and printing the shipping label on a first print renderingdevice that is disposed for communication with the first computerdevice.
 3. A shipping management computer system comprising at least onecomputer device that is programmed for: (A) receiving from a first userclient computer device through a first access path, an input by a firstuser of a set of parcel specifications corresponding to a transactionbetween the first user and the second user for a particular parcel to beshipped by the first user to a destination to be designated by a seconduser, said set of parcel specifications comprising: (1) an originaddress associated with the first user, and (2) at least one of: aparcel type, a set of parcel dimensions, a package weight, or a value ofthe particular parcel, (B) receiving from a second user client computerdevice through a second access path, an input by the second usercorresponding to the transaction between the first user and the seconduser of a set of recipient information for a delivery of the particularparcel to a destination indicated by the second user, said set ofrecipient information comprising: (1) a delivery address to which theparticular parcel is to be delivered, (2) a delivery service by whichthe particular parcel is to be delivered to the delivery address, and(3) a carrier that is to deliver the particular parcel to the deliveryaddress; (C) calculating a shipping rate corresponding to thetransaction between the first user and the second user, according to theinput by the first user and the input by the second user, for shippingthe particular parcel from the origin address to the delivery addressvia said delivery service and said carrier, wherein said computer systemis configured to calculate the shipping rate according to at least: (1)said parcel specifications; (2) said delivery address; (3) said deliveryservice; and (4) said carrier; and (D) displaying the shipping rate to asecond display device in communication with the second user clientcomputer device, wherein: said first user accesses the shippingmanagement computer system via the first access path through a globalcommunications network using the first user client computer device, andsaid second user accesses the shipping management computer system viathe second access path through the global communications network usingthe second user client computer device.
 4. The shipping managementcomputer system of claim 3, wherein said at least one computer device isfurther programmed for: displaying to the second display device incommunication with the second user client computer device used by asecond user, a list of permissible payment methods; and receiving aselection of a particular payment method from the list of permissiblepayment methods, said particular payment method selected by the seconduser to pay for: (A) a purchase of an item by the second user from thefirst user, and (B) a shipment of the item in the particular parcel fromthe first user to the second user.
 5. The shipping management computersystem of claim 4, wherein said at least one computer device is furtherprogrammed for: reporting to the first user client computer device areceipt of a payment for the purchase of the item and for shipment ofthe item.
 6. The shipping management computer system of claim 4, whereinsaid at least one computer device is further programmed for: generatinga shipping label for shipping the particular parcel from the originaddress associated with the first user, to the delivery address to whichthe particular parcel is to be delivered; and printing the shippinglabel on a first print rendering device in communication with the firstuser client computer device.